New Encryption Options
The new multiple encryption type support in Kerberos 5 also means that there can be more than one encryption type used in a given Kerberos protocol transaction. A separate encryption type can be used in each of the following messages:
- Ticket
The encryption type associated with the ticket is the encryption type used to encrypt the service ticket in the TGS or AS reply. Since the ticket can only be decrypted by the service, as it is encrypted with the service’s encryption key, the ticket encryption type is determined by the highest strength encryption supported by the service for which the ticket is issued.
- Reply
The encryption type of the reply from the KDC to the client refers to the part of the reply encrypted with the user’s encryption key. Since the client must decrypt the reply, the reply encryption type is determined by the highest strength encryption the client supports.
- Session key
Since the session key is shared between the client and the application server, the encryption type of the session key is the maximum-strength encryption algorithm that is supported by both the service and the client. For example, if the client supports single and triple DES but the service only supports single DES, then the KDC will issue single DES session keys for this service.
A diagram showing where each encryption key comes into play in a typical TGS reply is shown in Figure 3-10.
Why the separation? Namely, to support interoperation ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access