Your browser does not allow storing cookies. We recommend enabling them.
From SSH Tectia Client on Unix to SSH Tectia Server on z/OS
In this example, SSH Tectia Client 5.1 on Unix is used. For more information, see SSH Tectia Client 5.x User Manual.
To enable public-key authentication from SSH Tectia Client on Unix to SSH Tectia Server on z/OS:
- 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 1536 -P $HOME/.ssh2/unix_key
Generating 1536-bit rsa key pair
1536-bit rsa, user1@tectia_unix, Tue Jul 11 2006 14:49:51 +0300
Private key saved to /home/user1//.ssh2/unix_key
Public key saved to /home/user1//.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 on the z/OS Server (if it does not exist already):
$ sshg3 user1@tectia_zos 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 user1@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 © 2007 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Want to see how PrivX can help your organisation? Are you a DEVELOPER accessing cloud hosts, are you a IT ADMIN managing access & credentials in your corporation, are you BUSINESS MANAGER and want to save money or are you responsible of IT SECURITY in DevOps