=head1 NAME KeyFile - Defines AFS server encryption keys =head1 DESCRIPTION The F file defines the server encryption keys that the AFS server processes running on the machine use to decrypt the tickets presented by clients during the mutual authentication process. AFS server processes perform privileged actions only for clients that possess a ticket encrypted with one of the keys from the file. The file must reside in the F directory on every server machine. For more detailed information on mutual authentication and server encryption keys, see the I. Each key has a corresponding a key version number that distinguishes it from the other keys. The tickets that clients present are also marked with a key version number to tell the server process which key to use to decrypt it. The F file must always include a key with the same key version number and contents as the key currently listed for the C> principal in the associated Kerberos v5 realm or Authentication Database. (The principal C may be used if the cell and realm names are the same, but adding the cell name to the principal is recommended even in this case. C must be used as the principal name if the cell uses the Authentication Server rather than a Kerberos v5 realm.) The key must be a DES key; no stronger encryption type is supported. The F file is in binary format, so always use either the B command or the appropriate commands from the B command suite to administer it: =over 4 =item * The B or B command to add a new key. =item * The B or B command to display the keys. =item * The B or B command to remove a key from the file. =back The B commands must be run on the same server as the F file to update. The B commands may be run remotely. Normally, new keys should be added from a Kerberos v5 keytab using B. B is normally only used if the Authentication Server is in use instead of a Kerberos v5 realm. In cells that use the Update Server to distribute the contents of the F directory, it is customary to edit only the copy of the file stored on the system control machine. Otherwise, edit the file on each server machine individually. =head1 CAUTIONS The most common error caused by changes to F is to add a key that does not match the corresponding key for the Kerberos v5 principal or Authentication Server database entry. Both the key and the key version number must match the key for the corresponding principal, either C> or C, in the Kerberos v5 realm or Authentication Database. For a Kerberos v5 realm, that principal must only have DES encryption types in the Kerberos KDC. In the unusual case of using B to add a key with a known password matching a password used to generate Kerberos v5 keys, the keys in the Kerberos v5 KDC database must use C salt, not the default Kerberos v5 salt. The salt doesn't matter for the more normal procedure of extracting a keytab and then adding the key using B. =head1 SEE ALSO L, L, L, L, L, L, L The I at L. =head1 COPYRIGHT IBM Corporation 2000. All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.