Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server for IBM z/OS >>
    Getting Started with SSH Tectia Server for IBM z/OS >>
    Setting up Non-Interactive Server and User Authentication >>
        Key Distribution Tool
        Authenticating Remote Server Hosts >>
        Using Password for User Authentication
        Using Public Key for User Authentication
            Distributing Mainframe User Keys
    Setting up Non-Interactive Secure File Transfer >>

Distributing Mainframe User Keys

Administrators and other people can use passwords or public-key pairs with a passphrase-protected private key to access remote machines with SSH Tectia client tools from a Telnet or Secure Shell session. They can also use public-key pairs with a null passphrase if they want to run the SSH Tectia client programs in JCL.

Mainframe batch users are accounts that represent applications or subsystems, not people. They are set up with public-key pairs with a null passphrase to enable non-interactive access through JCL to remote servers. One key pair is generated for each batch user. If the batch user has a shared home directory, the key is placed in the shared $HOME/.ssh2 directory, otherwise it is copied to the user's home directories on all the LPARs.

When the ssh-keygen-g3 (or ssh-keydist-g3) tool is run with the -P option, which requests a null passphrase, it can be run from the OMVS shell or in JCL. It must be run under the batch user's user ID in order for the file permissions to be set properly.

The batch user accesses the remote machine using an account created and administered on the remote machine. The remote username may either be the same as the batch user's RACF user ID, or the same but in lower case, or a different username. Several batch users may use the same remote account. One batch user may use separate accounts on one remote machine for different accesses.

Each batch user's public key must be distributed to all the remote accounts it will be accessing. The way the public key is set up differs between SSH Tectia and OpenSSH. The ssh-keydist-g3 script must be told which type of server the remote machine has. The server must be running when ssh-keydist-g3 is run.

ssh-keydist-g3 uses password authentication for this initial access to the remote server. The password for the remote account can be entered in a dataset or in a file. See Sections File and Dataset for instructions. The filename is entered as one of the options in the ssh-keydist-g3 command.

The other options needed on the ssh-keydist-g3 command line are the remote account username, the remote host DNS name or IP address, and the type of the remote Secure Shell server (SSH Tectia Server on Unix, SSH Tectia Server on Windows, SSH Tectia Server for IBM z/OS on mainframe, or OpenSSH on Unix).

Password from File

To set up password-from-file authentication:

  1. Create a file, for example /home/userid/passwd_file.
  2. Make sure the file is readable only by the user that created it:
    > chmod 600 /home/userid/passwd_file
  3. Edit the file with your favorite text editor to contain one line with your password on the remote system, for example:

Password from Dataset

To set up password-from-dataset authentication:

  1. Allocate a dataset or a dataset member, for example:
  2. Make sure that the dataset is accessible only by the correct UserID.
  3. Edit the password dataset to contain your password on the remote system. The format of the password dataset is one line containing only the password. For example:

Examples of Distributing User Keys

The following examples illustrate using ssh-keydist-g3 for distributing user keys.

Example 1: Public-Key Upload to Unix OpenSSH Server from USS Shell

This command creates a 1024-bit RSA key with an empty passphrase and uploads it to a Unix server running OpenSSH, including the necessary conversions. Public-key upload uses password-from-file for authentication. A log of the operation is stored under /tmp. The example assumes that the server host key has already been fetched and verified.

> ssh-keydist-g3 --key-type rsa --key-bits 1024 --empty-passphrase \
   --remote-user userid --password-file /home/userid/passwd_file \
   --user-key-log /tmp/my_log_file --openssh-unix

Example 2: Public-Key Upload to Unix OpenSSH Server Using JCL

This example KEYDIST from SAMPLIB presents a JCL script that does the same steps as the USS command in Example 1 above (options are given in short format):

//             REGION=0M
//             DISP=SHR
  BPXBATCH SH  /opt/tectia/bin/ssh-keydist-g3 +
               -t rsa -b 1024 -P +
               -u userid -p "//'USERID.PASSWD'" +
               -U /tmp/my_log_file +
//             PATHOPTS=(ORDONLY),
//             PATHDISP=(DELETE,KEEP),
//             DCB=(LRECL=4000,RECFM=VB)
//             PATHOPTS=(ORDONLY),
//             PATHDISP=(DELETE,KEEP),
//             DCB=(LRECL=4000,RECFM=VB)

Example 3: Public-Key Distribution to Multiple Hosts from USS Shell

This example distributes an existing public key to several remote hosts automatically. Individual user names can be defined for each server. Server type (SSH Tectia Unix, SSH Tectia Windows, SSH Tectia z/OS, OpenSSH) needs to be defined with the flags: -S, -W, -Z, or -O. The example assumes that the relevant server host keys have already been fetched and verified.

In this example you can find four server "blocks":

  • -O -u user1
  • -S -u user2
  • -W -u user2
  • -Z -u user3

A password file is defined for each separate user ID. user2 is assumed to have the same password on Unix and Windows. A log of the operation is stored under /tmp.

The command is as follows:

> ssh-keydist-g3 -f /home/userid/.ssh2/ \
   -U /tmp/userkeys.log \
   -p /home/userid/passwd_file1 \
   -O -u user1 \
   -p /home/userid/passwd_file2 \
   -S -u user2 \ 
   -W -u user2 \ 
   -p /home/userid/passwd_file3 \
   -Z -u user3

PreviousNextUp[Contents] [Index]

[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]

Copyright © 2011 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice




What to read next:

  • 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.
    Download now
  • 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.
    Download now