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

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server (M) >>
        System Requirements
        Directories and Datasets>>
        Installing the SSH Tectia Server (M) Software >>
            Required Permissions
            Preparing the System
            Unpacking the Archive
            Creating the SSHD2 User
            Creating the /usr/lpp/ssh2 Directory
            Running the Setup Script
            Creating the Server Host Key Pair
            Enabling Manual Pages
            Securing the Server
        Upgrading the SSH Tectia Server (M) Software
        Removing the SSH Tectia Server (M) Software
    Using SSH Tectia Server (M) >>
    Troubleshooting SSH Tectia Server (M) >>
    Configuration >>
    Authentication >>
    Application Tunneling >>
    Sample Files >>
    Man Pages
    Log Messages >>

Creating the /usr/lpp/ssh2 Directory

SSH Tectia Server (M) always installs to /usr/lpp/ssh2. You have several options of how to create the ssh2 directory.

Option 1:

If you want to put the product into a separate HFS or ZFS file system, make an empty ssh2 directory under /usr/lpp:

>cd /usr/lpp
>mkdir ssh2

Create the file system and mount it on /usr/lpp/ssh2. You can use the CREAHFS and MOUNHFS SAMPLIB examples (see Appendix CREAHFS and MOUNHFS). The sample files are for HFS but ZFS can also be used. Note that mounting the file system causes an operator query that must be responded to. You may want to copy the mount command into the BPXPRMxx member in PARMLIB so that the file system is mounted each time you IPL the system.

Option 2:

If you want to install the product into an existing file system, for example the one where /opt is mounted, make an empty directory in that file system and create a link to it under /usr/lpp:

>mkdir /opt/ssh_5_0
>cd /usr/lpp
>ln -s /opt/ssh_5_0 ssh2

Option 3:

If you do neither of the above, the product will go into the file system where /usr/lpp is. In all cases the path to the product will be /usr/lpp/ssh2.

Ensure that the /usr/lpp/ssh2 directory is writable and that it is owned by the SSHD2 user:

>chmod 755 /usr/lpp/ssh2
>chown SSHD2:0 /usr/lpp/ssh2

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




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