for details and how to disable cookies.
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.
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
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
file on the remote z/OS
$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). [ Contents] [ Index] [ 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. Copyright Notice