SSH Tectia  
Previous Next Up [Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server for IBM z/OS >>
    Getting Started with SSH Tectia Server for IBM z/OS >>
    Configuring the Server >>
    Configuring the Client >>
    Authentication >>
        Using the z/OS System Authorization Facility
        Server Authentication with Public Keys in File >>
        Server Authentication with Certificates >>
        User Authentication with Passwords
        User Authentication with Public Keys in File >>
            From SSH Tectia Client on z/OS
            From SSH Tectia Client on Windows to SSH Tectia Server on z/OS
            From SSH Tectia Client on Unix to SSH Tectia Server on z/OS
            From OpenSSH Client on Unix to SSH Tectia Server on z/OS
            Settings in SSH Tectia Server on z/OS
        User Authentication with Certificates >>
        Host-Based User Authentication >>
        User Authentication with Keyboard-Interactive >>
        Distributing Public Keys Using the Key Distribution Tool >>
    File Transfer Using SFTP >>
    File Transfer Using Transparent FTP Tunneling >>
    Tunneling on the Command Line >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Advanced Information >>
    Man Pages >>
    Log Messages >>

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:

  1. Create a key pair using ssh-keygen-g3. For non-interactive use, the key can be generated without a passphrase with the -P option.
    $ ssh-keygen-g3 -t rsa -b 1536 -P $HOME/.ssh2/unix_key
    Generating 1536-bit rsa key pair
       5 oOo.oOo.oOo.
    Key generated.
    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
    
  2. 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 
    IdKey unix_key
    
  3. Create a remote .ssh2 directory on the z/OS Server (if it does not exist already):
    $ sshg3 user1@tectia_zos mkdir .ssh2
    
  4. Copy your public key to the remote z/OS Server:
    $ scpg3 unix_key.pub \
    user1@zos:/ftadv:C=ISO8859-1,D=IBM-1047,X=TEXT/.ssh2/unix_key.pub
    
  5. Create an authorization file on the remote z/OS Server.
    $ sshg3 user1@zos "echo Key unix_key.pub >> .ssh2/authorization"
    
  6. 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).

Previous Next Up [Contents] [Index]


[ 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.
Copyright Notice