Your browser does not allow storing cookies. We recommend enabling them.


Creating Keys with ssh-keygen-g3 on z/OS

To create a public key pair, run ssh-keygen-g3 on Client:

$ ssh-keygen-g3
Generating 2048-bit rsa key pair
   9 oOo.oOo.oOo
Key generated.
2048-bit rsa, ClientUser@Client, Wed Feb 2 2016 12:09:46 +0200
Passphrase : 
Again :
Private key saved to  /home/ClientUser/.ssh2/id_rsa_2048_a
Public key saved to   /home/ClientUser/.ssh2/

When run without options, ssh-keygen-g3 asks for a passphrase for the new key. Enter a sufficiently long (20 characters or so) sequence of any characters (spaces are OK).

The new authentication key pair consists of two separate files. One of the keys is your private key which must never be made available to anyone but yourself. The private key can only be used together with the passphrase.

The key pair is by default stored in your $HOME/.ssh2 directory (created by ssh-keygen-g3 if it does not exist previously).

In the example above, the private key file is id_rsa_2048_a. The public key file is, and it can be distributed to other computers.

By default, ssh-keygen-g3 creates a 2048-bit RSA key pair. DSA or ECDSA keys can be generated by specifying the -t option with ssh-keygen-g3. Key length can be specified with the -b option. For automated jobs, the key can be generated without a passphrase with the -P option, for example:

$ ssh-keygen-g3 -t ecdsa -b 384 -P 

For more information on the ssh-keygen-g3 options, see ssh-keygen-g3(1).




What to read next:

  • 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