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 >>
    Using SSH Tectia Server for IBM z/OS >>
    Configuring the Server >>
    Configuring the Client >>
    Authentication >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Examples of Use >>
        Secure File Transfers Using the z/OS Client>>
        Secure File Transfers Using Windows and Unix Clients>>
        Submitting JCL Jobs over Secure Shell
        Debugging SSH Tectia Server for IBM z/OS>>
        Example of Distributing Keys >>
            Mainframe Server Keys
            Remote Server Keys
            Mainframe User Keys
            Remote User Keys
    Man Pages >>
    Log Messages >>

Mainframe Server Keys

The server is run as a started task under the SSHD2 user as described in Section Running as a Started Task, one server on each LPAR that will be accessed.

Each system (LPAR) has its own /etc/ssh2 directory. A server key is generated for each system. The Mainframe Security Group publishes the fingerprints of these keys.

The remote users download the server public key on the first Secure Shell access to the mainframe and whenever the server key has been changed. This access must be interactive and the user must verify the key by its fingerprint and allow the Secure Shell client program to write it to the user's $HOME/.sshx directory. The directory is $HOME/.ssh2/hostkeys for SSH Tectia Client on Unix and $HOME/.ssh/known_hosts for OpenSSH clients. SSH Tectia Client on Windows stores the key in the "%USERPROFILE%\Application Data\SSH\HostKeys" directory.

To set up client access, the users must access all the mainframe systems. When this is done, accessing the mainframe only requires the users to enter their passwords.

PreviousNextUp[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


 

 
Highlights from the SSH.COM blog:

  • 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