Check that you have the operating system fully patched. See the latest patch information on the Hewlett-Packard web site. In case PAM/Kerberos is used on a HP-UX platform, install also the latest patches related to Kerberos.
The downloaded installation package contains the compressed installation files.
Two packages are required: one for the common components of Tectia Client and Server, and one for the specific components of Tectia Server.
To install Tectia Server on HP-UX, follow the instructions below:
Unpack the downloaded
Make sure no other software is using port 22 (Tectia Server default listen port). Stop any competing server software or change their listen port.
Select the installation package according to your HP-UX version.
When installing on HP-UX 11i v1 (11.11), 11i v2 (11.23), or 11i v3 (11.31) running on the PA-RISC architecture, select the following packages:
When installing on HP-UX 11i v2 or 11i v3 running on the Itanium architecture, select the following packages:
In the commands,
<version>indicates the product release version and the current build number (for example,
Unpack the installation packages with
uncompress. In order to be installable, the created packages must have the correct long file names. In the following command examples, we use the Itanium packages:
$ uncompress ssh-tectia-common-
<version>-hpux-11i-ia64.depot.Z $ uncompress ssh-tectia-server-
Install the packages by running the following commands with root privileges:
# swinstall -s
<version>-hpux-11i-ia64.depot SSHG3common # swinstall -s
In the commands,
<path>is the full path to the installation package.
HP-UX requires the full path even when the command is run in the same directory.
The server host key is generated during the installation. The key generation may take several minutes on slow machines.
Copy the license file to the
/etc/ssh2/licensesdirectory. (This is not necessary in "third-digit" maintenance updates.) See Licensing.
If this is the initial installation of Tectia Server, 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.
The installation should (re)start the server automatically.
If the server does not start (for example because of a missing license or because some other secure shell software is running on port 22), you can start it after correcting the problem by issuing the command:
# /sbin/init.d/ssh-server-g3 start