Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.

SSH

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 dsa key pair
   9 oOo.oOo.oOo
Key generated.
2048-bit dsa, ClientUser@Client, Thu Jan 2 2014 12:09:46 +0200
Passphrase : 
Again :
Private key saved to  /home/ClientUser/.ssh2/id_dsa_2048_a
Public key saved to   /home/ClientUser/.ssh2/id_dsa_2048_a.pub

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_dsa_2048_a. The public key file is id_dsa_2048_a.pub, and it can be distributed to other computers.

By default, ssh-keygen-g3 creates a 2048-bit DSA key pair. RSA 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 rsa -b 1536 -P 

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

===AUTO_SCHEMA_MARKUP===