48.6.6. Configuring a Kerberos 5 Client
Setting up a Kerberos 5 client is less involved than setting up a server. At a minimum, install the client packages and provide each client with a valid
krb5.confconfiguration file. While
sloginare the preferred method of remotely logging in to client systems, Kerberized versions of
rloginare still available, though deploying them requires that a few more configuration changes be made.
- Be sure that time synchronization is in place between the Kerberos client and the KDC. Refer to Section 48.6.5, “Configuring a Kerberos 5 Server” for more information. In addition, verify that DNS is working properly on the Kerberos client before configuring the Kerberos client programs.
- Install the
krb5-workstationpackages on all of the client machines. Supply a valid
/etc/krb5.conffile for each client (usually this can be the same
krb5.conffile used by the KDC).
- Before a workstation in the realm can use Kerberos to authenticate users who connect using
rlogin, it must have its own host principal in the Kerberos database. The
klogindserver programs all need access to the keys for the host service's principal. Additionally, in order to use the kerberized
rloginservices, that workstation must have the
kadmin, add a host principal for the workstation on the KDC. The instance in this case is the hostname of the workstation. Use the
-randkeyoption for the
addprinccommand to create the principal and assign it a random key:
addprinc -randkey host/blah.example.comNow that the principal has been created, keys can be extracted for the workstation by running
kadminon the workstation itself, and using the
ktadd -k /etc/krb5.keytab host/blah.example.com
- To use other kerberized network services, they must first be started. Below is a list of some common kerberized services and instructions about enabling them:
Refer to Chapter 18, Controlling Access to Services for details about how to enable services.
ssh— OpenSSH uses GSS-API to authenticate users to servers if the client's and server's configuration both have
GSSAPIAuthenticationenabled. If the client also has
GSSAPIDelegateCredentialsenabled, the user's credentials are made available on the remote system.
rlogin— To use the kerberized versions of
- Telnet — To use kerberized Telnet,
krb5-telnetmust be enabled.
- FTP — To provide FTP access, create and extract a key for the principal with a root of
ftp. Be certain to set the instance to the fully qualified hostname of the FTP server, then enable
- IMAP — To use a kerberized IMAP server, the
cyrus-imappackage uses Kerberos 5 if it also has the
cyrus-sasl-gssapipackage installed. The
cyrus-sasl-gssapipackage contains the Cyrus SASL plugins which support GSS-API authentication. Cyrus IMAP should function properly with Kerberos as long as the
cyrususer is able to find the proper key in
/etc/krb5.keytab, and the root for the principal is set to
kadmin).An alternative to
cyrus-imapcan be found in the
dovecotpackage, which is also included in Red Hat Enterprise Linux. This package contains an IMAP server but does not, to date, support GSS-API and Kerberos.
- CVS — To use a kerberized CVS server,
gserveruses a principal with a root of
cvsand is otherwise identical to the CVS