SSH Tectia

Installing on HP-UX

SSH Tectia Server is available for:

In case PAM/Kerberos is used, install also the latest patches related to Kerberos. Get the latest versions from the Hewlett-Packard web site.

SSH Tectia Server includes support for Entrust certificates on HP-UX 11.0. The necessary libraries are automatically included in the installation.

On the CD-ROM, the installation packages for HP-UX platforms are located in the /install/hp-ux/ directory. Two packages are required: one for the common components of SSH Tectia Client and Server, and another for the specific components of SSH Tectia Server.

To install SSH Tectia Server on HP-UX, follow the instructions below:

  1. (Not necessary in "third-digit" maintenance updates.) Copy the license file to the /etc/ssh2/licenses directory. See Licensing.

    If this is the initial installation of SSH Tectia Server 5.x, the directory does not yet exist. You can either create it manually or copy the license after the installation. In the latter case, you have to start the server manually after copying the license file.

  2. Unpack the packages with gunzip. In order to be installable, the created packages must have the correct long file name:

    $ gunzip ssh-tectia-common-<ver>-sd-<arch>.depot.Z
    $ gunzip ssh-tectia-server-<ver>-sd-<arch>.depot.Z

    In the package name, <ver> is the current package version of SSH Tectia Server (for example, and <arch> is the version and architecture of the HP-UX operating system (11.00-pa-risc for HP-UX on PA-RISC or 11.22-itanium for HP-UX on Itanium).

  3. Install the packages by running the following command with root privileges:

    # swinstall -s <path>/ssh-tectia-common-<ver>-sd-<arch>.depot SSHG3common
    # swinstall -s <path>/ssh-tectia-server-<ver>-sd-<arch>.depot SSHG3server

    In the command, <path> is the full path to the installation package (HP-UX requires this even when the command is run in the same directory).

    The server host key is generated during the installation. Key generation may take several minutes on slow machines.

  4. The installation should (re)start the server automatically.

    If the server does not start (because of a missing license, for example), you can start it after correcting the problem by issuing the command:

    # /sbin/init.d/ssh-server-g3 start