All commands in this section are shown using the SSH Tectia z/OS client. Server-side configuration can also be done by logging in to the remote server and entering the commands locally.
To set up user public-key authentication from a z/OS Client, do the following steps:
Create a key pair by executing ssh-keygen2 on the z/OS client host.
By default, ssh-keygen2 creates a 2048-bit DSA key pair. RSA keys can be generated by specifying the -t rsa option. Key length can be specified with the -b option. For non-interactive use, the key can be generated without a passphrase with the -P option.
You now have an identification file that consists of one line that denotes the file containing your identification (your private key). For special applications, you can create multiple identifications by executing ssh-keygen2 again. However, this is not usually needed.
Create a .ssh2 or .ssh directory on Server (if it does not exist already).
If the remote host is running SSH Tectia Server on Unix or z/OS :
$ ssh2 testuser@tectia_server mkdir .ssh2
If the remote host is running SSH Tectia Server on Windows:
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