Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Using alternate LU key-encrypting key names z/OS Communications Server: SNA Network Implementation Guide SC27-3672-01 |
|
To encipher the session key that is sent to the LU when a session is established, the control point (CP or SSCP) that owns the LU uses the LU master key in the cryptographic key data set (CKDS). When changing the LU master key, a similar change must also be made in the CKDS at the control point. Otherwise, the LU would have the new key and the CP would have the old key. By specifying the CKEY operand VTAM® uses an alternate key-encrypting-key (KEK) name that matches the LU master key while the primary master key is being changed in the CKDS. The CKEY operand can be specified on the MODEENT macro in the logon mode table or on the MODIFY SECURITY command. The KEK specified by the CKEY operand will be used during session activation until it is changed by the MODIFY SECURITY command or the LU is deactivated. Use of the CKEY operand eases the administration process involved when changing the LU master key. Without the CKEY, both the master key at the LU and in the CKDS must be done simultaneously. This in turn reduces the likeliness of a session failure because the LU master key and CKDS key are not the same. The CKEY allows for continued use of the alternate master key until both the CKDS and LU have been updated with the new primary master key. For VTAM to use the alternate LU KEK name while you change the LU master key, follow this general procedure:
See z/OS Communications Server: SNA Resource Definition Reference for details on the CKEY operand, and to z/OS Communications Server: SNA Operation for full details on the use of the MODIFY SECURITY command. |
Copyright IBM Corporation 1990, 2014
|