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
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 Cryptomining with the SSH protocol: what big enterprises need to know about it Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency. Read more SLAM the door shut on traditional privileged access management Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity? Read more We broke the IT security perimeter Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so. Read more SSH Webinar: The evolution of 3rd party access – four use cases Join Ubisecure and SSH.COM webinar on Tuesday 22 January to learn how cloudification has changed the rules of mission-critical access. What we recommend to read next: Regulatory compliance for cybersecurity? Privileged access management related information NEAREST SSH.COM OFFICE SSH Communications Security, Inc. 460 Totten Pond Road #460 Waltham, MA 02140 USA 781-247-2100 Contact us