Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server (M) >>
    Using SSH Tectia Server (M) >>
        Configuration Files>>
        Running the Server >>
        Setting Up a Shell User>>
            Authenticating Remote Hosts
            Using Password Authentication
            Using Public-Key Authentication
        Running Client Programs>>
        Handling MVS Datasets>>
        File Transfer Examples>>
    Troubleshooting SSH Tectia Server (M) >>
    Configuration >>
    Authentication >>
    Application Tunneling >>
    Sample Files >>
    Man Pages
    Log Messages >>

Authenticating Remote Hosts

Remote Secure Shell servers are authenticated by a public-key procedure. The user checks the fingerprint of the remote server's public key. When the user has approved the public key, it is stored in the user's $HOME/.ssh2 directory and will be used automatically thereafter.

The verification step requires user interaction, so even for users that are set up to run client programs unattended (Section Running Client Programs under MVS), the first connection, and every time the remote host's key is changed, must be done by a person who logs in as the user, accesses the remote server, and goes through the fingerprint check dialog.

See also Server Authentication with Public Keys.

PreviousNextUp[Contents] [Index]


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

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

===AUTO_SCHEMA_MARKUP===