code) type support in Kerberos 5 also means that there can be more than one (turning messages into secret code) type used in a given Kerberos rules of conduct transaction. A separate (turning messages into secret code) type can be used in each of the following messages: Ticket The (turning messages into secret code) type connected with the ticket is the (turning messages into secret code) type used to (turn into secret code) the service ticket in the TGS or AS reply. Since the ticket can only be (changed secret codes into readable messages) by the service, as it is secret/unreadable with the service's number-based key to secretly code messages, the ticket (turning messages into secret code) type is figured out by/decided by the highest strength (turning messages into secret code) supported by the service for which the ticket is issued. Reply The (turning messages into secret code) type of the reply from the KDC to the client refers to the part of the reply (turned into secret code) with the user's number-based key to secretly code messages. Since the client must (change secret codes into readable messages) the reply, the reply (turning messages into secret code) type is figured out by/decided by the highest strength (turning messages into secret code) the client supports. Session key Since the session key is shared between the client and the application server, the (turning messages into secret code) type of the session key is the maximum-strength (turning messages into secret code) set of computer instructions 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.