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 >>
        Configuration Files >>
            Editing Configuration Files
            Command-Line Options
            Recommended Algorithms for Mainframe Environment
            Crypto Hardware Support
            Configuration Options in Load-Balanced Environments
            Running SSH Tectia and OpenSSH in a z/OS Environment
        Subconfigurations >>
        Ciphers and MACs
        Compression
        Configuring Root Logins
        Restricting User Logins
        Subsystems
        Auditing >>
        Securing the Server >>
        Default sshd2_config Configuration File
        Default ssh_certd_config Configuration File
    Configuring the Client >>
    Authentication >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Examples of Use >>
    Man Pages >>
    Log Messages >>

Running SSH Tectia and OpenSSH in a z/OS Environment

SSH Tectia Server for IBM z/OS installs always under /usr/lpp/ssh2, so the SSH Tectia and OpenSSH binaries are not confused. Configuration files and host keys are stored in the /etc/ssh2 directory, compared to the /etc/ssh directory used by OpenSSH. User keys and other user-specific files are stored under $HOME/.ssh2, compared to $HOME/.ssh used by OpenSSH. The server port can be configured in the /etc/ssh2/sshd2_config file with the keyword Port. The default is 22, but it can be changed to any available port.

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