Your browser does not allow storing cookies. We recommend enabling them.
Certificates Stored in SAF
The following example assumes that the
SSHD2 user created in Section
Creating the SSHD2 User is used to run the server.
To use SAF certificates for authenticating the server, do the following steps. Replace the names and IDs with those appropriate to your system:
Create the server host key in SAF by giving the following TSO commands:
RACDCERT ID(SSHD2) GENCERT SUBJECTSDN(CN('LPAR1') OU('RD')
O('EXAMPLE')) SIZE(1024) WITHLABEL('LPAR1.EXAMPLE.COM')
RACDCERT ID(SSHD2) LIST
Give the following TSO command to generate the certification request:
RACDCERT ID(SSHD2) GENREQ(LABEL('LPAR1.EXAMPLE.COM'))
Use the PKCS#10 certification request in the dataset
'SSHD2.LPAR1.CRT.REQ' to enroll the certificate. The actual steps depend on your CA setup.
After the enrollment is completed, store the received certificate to a dataset, for example
To connect the new certificate to a key ring, give the following TSO commands:
RACDCERT ID(SSHD2) ADD('SSHD2.LPAR1.CRT') TRUST
RACDCERT ID(SSHD2) ADDRING(SSH-HOSTKEY)
RACDCERT ID(SSHD2) CONNECT(ID(SSHD2) LABEL('LPAR1.EXAMPLE.COM')
RACDCERT ID(SSHD2) LISTRING(SSH-HOSTKEY)
For the settings to take effect, give the following TSO command:
SETROPTS RACLIST(DIGTCERT) REFRESH
Define the z/OS SAF external key provider in the
HostKeyEkInitString "KEYS(ID(SSHD2) RING(SSH-HOSTKEY)
HostKeyEkInitString must point to a single private key. Setting the
HostKey.Cert.Required option to
yes defines that the server must authenticate with a certificate. When the z/OS SAF provider is used, setting the option to
no means that only the public key found in the SAF certificate is used. Setting the option to
optional means that both the SAF certificate and the public key found in the SAF certificate are used.
For more information on the configuration file options, see
sshd2_config. For information on the format of the external key initialization string, see ssh-externalkeys. [ Contents] [ Index] [ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]
Copyright © 2011 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved. Copyright Notice Reduce Secure Shell risk. Get to know the NIST 7966. The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government. Download now ISACA Practitioner Guide for SSH With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community. Download now What we recommend to read next: Regulatory compliance for cybersecurity? Privileged access management related information NEAREST SSH.COM OFFICE SSH Communications Security, Inc. 460 Totten Pond Road #460 Waltham, MA 02140 USA 781-247-2100 Contact us