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

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server >>
        Planning the Installation >>
        Installing the SSH Tectia Server Software >>
            Installing on AIX
            Installing on HP-UX
            Installing on Linux
            Installing on Solaris
        Removing the SSH Tectia Server Software >>
    Getting Started >>
    Configuration >>
    Authentication >>
    Application Tunneling >>
    Troubleshooting >>
    Man Pages
    Advanced Options >>
    Log Messages >>

Installing on AIX

On the CD-ROM, the AIX binaries are located in the directory /install/aix/. Separate packages are available for AIX 4.3 and for AIX 5L. Please read the README file for any important last-minute information.

Note: You need GNU gzip in order to install SSH Tectia Server on AIX.

To install SSH Tectia Server on AIX, do the following:

  1. (Not necessary in "third-digit" maintenance updates.) Copy the license file as instructed in Section Licensing.
  2. (If installing from CD-ROM.) Copy the installation package to your machine.
  3. Unpack the package using the following command:
    $ gzip -d ssh-secure-shell-<v>-<aix-v>.bff.gz
    In the command, <v> is the current package version of SSH Tectia Server (for example, and <aix-v> is the version of the AIX operating system (aix4.3 or aix5.x).
  4. Install the package by issuing the following command with root privileges:
    # installp -d ssh-secure-shell-<v>-<aix-v>.bff SSH.Secure.Shell
    If you only want to apply the package (and not commit it), give the following command:
    # installp -a -d ssh-secure-shell-<v>-<aix-v>.bff SSH.Secure.Shell
    Packages which are applied but not committed can be rejected later on. This is useful if you have a previous version installed (lslpp -l SSH.Secure.Shell). Please read the AIX manual pages for more information about the installp command. You can also install the package using smit.
  5. The installation should (re)start the server daemon automatically. If the daemon does not start (because of a missing license, for example), you can start it after correcting the problem by issuing the command:
    # /etc/ssh2/sshd2 restart
    Or alternatively:
    # /usr/local/sbin/sshd2

Enabling FIPS (Optional)

For a list of platforms on which the FIPS library has been validated or tested, see SSH Tectia Client/Server Product Description.

To enable the FIPS-certified mode, run the following command:

# /usr/local/sbin/ssh-crypto-library-chooser fips

This will set the library symlinks, so that sshd2 and ssh2 will use the FIPS-certified crypto library. You can change back to using the standard crypto library by running the following command:

# /usr/local/sbin/ssh-crypto-library-chooser std

You can query the current library status by running the script without arguments. This will show the current symlink target (libsshcrypto-std or libsshcrypto-fips).

PreviousNextUp[Contents] [Index]

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

Copyright © 2010 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