Your browser does not allow storing cookies. We recommend enabling them.
Using Public-Key Authentication from Unix Client to z/OS Server
In this example, SSH Tectia Client 5.1 is used. For more information, see SSH Tectia Client 5.x User Manual.
- Create a key pair using
ssh-keygen-g3. For non-interactive use, the key can be generated without a passphrase with the
$ ssh-keygen-g3 -t rsa -b 1024 -P $HOME/.ssh2/unix_key
Generating 1024-bit rsa key pair
1024-bit rsa, testuser@unix_server, Tue Jul 11 2006 14:49:51 +0300
Private key saved to /home/testuser//.ssh2/unix_key
Public key saved to /home/testuser//.ssh2/unix_key.pub
- Create an
identification file in your
$HOME/.ssh2 directory on the Unix Client, for example:
$ cd $HOME/.ssh2
$ echo "IdKey unix_key" >identification
$ cat identification
- Create a remote
.ssh2 directory (if it does not exist already).
$ssh2 testuser@tectia_mf_server mkdir .ssh2
- Copy your public key to the remote z/OS Server.
$ scpg3 unix_key.pub
- Create an
file on the remote z/OS Server.
$sshg3 testuser@zos "echo Key unix_key.pub > .ssh2/authorization"
- Make sure that public-key authentication is allowed in the Connection Broker configuration on Client, in the default settings and in the relevant connection profile (it is allowed by default).
[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]
Copyright © 2006 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
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.
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.