MIT krb5 - Revision history

Oppiz at 17:36, 20 September 2009

2009-09-20T17:36:20Z

← Older revision		Revision as of 17:36, 20 September 2009
Line 7:		Line 7:
	----		----

	{{~~Blank-~~Package-Introduction}}		{{Package-Introduction\|Kerberos is a network authentication protocol. It is designed to provide strong authentication for client/server applications by using secret-key cryptography. A free implementation of this protocol is available from the Massachusetts Institute of Technology.\|http://web.mit.edu/Kerberos/}}

	== Dependencies ==		== Dependencies ==

2009-06-07T00:12:50Z

64Bit

← Older revision		Revision as of 00:12, 7 June 2009
Line 153:		Line 153:
	mv -v /usr/lib64/libcom_err.so.3* /lib64 &&		mv -v /usr/lib64/libcom_err.so.3* /lib64 &&
	mv -v /usr/lib64/libgssapi_krb5.so.2* /lib64 &&		mv -v /usr/lib64/libgssapi_krb5.so.2* /lib64 &&
	mv -v /usr/lib64/libgssrpc.so.4* /~~li64b~~ &&		mv -v /usr/lib64/libgssrpc.so.4* /lib64 &&
	mv -v /usr/lib64/libk5crypto.so.3* /lib64 &&		mv -v /usr/lib64/libk5crypto.so.3* /lib64 &&
	mv -v /usr/lib64/libkadm5clnt.so.6* /lib64 &&		mv -v /usr/lib64/libkadm5clnt.so.6* /lib64 &&

2009-06-07T00:09:13Z

2009-02-08T20:45:39Z

← Older revision		Revision as of 20:45, 8 February 2009
Line 440:		Line 440:
	\| is an all-purpose Kerberos 5 library.		\| is an all-purpose Kerberos 5 library.
	\|}		\|}

			[[Category:General Libs]]

2008-11-30T18:47:43Z

← Older revision		Revision as of 18:47, 30 November 2008
Line 194:		Line 194:
	{{Note\|'''login.krb5''' does not support shadow passwords. So, when the Kerberos server is unavailable, the default use of '''/etc/passwd''' will not work because the passwords are now in '''/etc/shadow''' (where they were put while building CLFS). Entering the following commands without moving the passwords back to '''/etc/passwd''' could prevent any logins.}}		{{Note\|'''login.krb5''' does not support shadow passwords. So, when the Kerberos server is unavailable, the default use of '''/etc/passwd''' will not work because the passwords are now in '''/etc/shadow''' (where they were put while building CLFS). Entering the following commands without moving the passwords back to '''/etc/passwd''' could prevent any logins.}}

	If you have [[Linux-PAM]] installed then you can authenticate using the login provided by shadow through the [[~~pam_krb5~~]] module (Recommended). If you understand the above warning and [[Linux-PAM]] is not installed, the following commands can be used:		If you have [[Linux-PAM]] installed then you can authenticate using the login provided by shadow through the [[Pam-krb5]] module (Recommended). If you understand the above warning and [[Linux-PAM]] is not installed, the following commands can be used:

	mv -v /bin/login /bin/login.shadow &&		mv -v /bin/login /bin/login.shadow &&

2008-11-16T14:54:34Z

Configuring

← Older revision		Revision as of 14:54, 16 November 2008
Line 201:		Line 201:
	The information in the sections below are based off information from the following pages:		The information in the sections below are based off information from the following pages:

	http://www.bayour.com/LDAPv3-HOWTO.~~htm~~		http://www.bayour.com/LDAPv3-HOWTO.html
	http://aput.net/~jheiss/krbldap/		http://aput.net/~jheiss/krbldap/

2008-11-16T00:36:49Z

Creating a Kerberos Realm

← Older revision		Revision as of 00:36, 16 November 2008
Line 223:		Line 223:
	[kdc]		[kdc]
	profile = /var/lib/krb5kdc/kdc.conf		profile = /var/lib/krb5kdc/kdc.conf

			[appdefaults]
			pam = {
			''<REALMNAME.COM>'' = {
			minimum_uid = 5000
			}
			}

	[realms]		[realms]
	<REALMNAME.COM> = {		''<REALMNAME.COM>'' = {
	kdc = ''<servername.realmname.com>''		kdc = ''<servername.realmname.com>''
	admin_server = ''<servername.realmname.com>''		admin_server = ''<servername.realmname.com>''

2008-11-15T21:20:07Z

Configuring

← Older revision		Revision as of 21:20, 15 November 2008
Line 194:		Line 194:
	{{Note\|'''login.krb5''' does not support shadow passwords. So, when the Kerberos server is unavailable, the default use of '''/etc/passwd''' will not work because the passwords are now in '''/etc/shadow''' (where they were put while building CLFS). Entering the following commands without moving the passwords back to '''/etc/passwd''' could prevent any logins.}}		{{Note\|'''login.krb5''' does not support shadow passwords. So, when the Kerberos server is unavailable, the default use of '''/etc/passwd''' will not work because the passwords are now in '''/etc/shadow''' (where they were put while building CLFS). Entering the following commands without moving the passwords back to '''/etc/passwd''' could prevent any logins.}}

	If you understand the above warning and [[Linux-PAM]] is not installed, the following commands can be used:		If you have [[Linux-PAM]] installed then you can authenticate using the login provided by shadow through the [[pam_krb5]] module (Recommended). If you understand the above warning and [[Linux-PAM]] is not installed, the following commands can be used:

	mv -v /bin/login /bin/login.shadow &&		mv -v /bin/login /bin/login.shadow &&

2008-11-15T21:05:31Z

Configuring Kerberos Clients

← Older revision		Revision as of 21:05, 15 November 2008
Line 310:		Line 310:

	=== Configuring Kerberos Clients ===		=== Configuring Kerberos Clients ===

			Securly copy '''/etc/krb5.conf''' from one of the Kerberos Servers to each of the clients. You should now be able to get a ticket from the KDC. Now would be a good time to test this:

			kinit ''<principal name>''

			List your tickets with the following command:

			klist

	= Contents =		= Contents =

2008-11-15T20:59:22Z

Dependencies