Installing on Linux
SSH Tectia Client and Server for Linux platforms are supplied in RPM (Red Hat Package Manager) binary packages. The RPMs are available for Red Hat and SUSE Linux running on Intel x86 (
i386), on IBM POWER (
ppc64pseries), and on IBM S/390 or zSeries (
s390) platforms. The package for the x86 architecture is compatible also with the 64-bit version of Red Hat Enterprise Linux 4 running on x86-64 platform. The IBM Linux packages are not available with SSH Tectia Server (A).
On other platforms that use the RPM package manager, the installation of the appropriate files will probably succeed, but the configuration phase might fail. In this case, you must do the configuration manually, as if you were installing directly from source files (see Appendix Installation on Other Unix Platforms).
Note: SSH Tectia Server on Linux requires the termcap libraries. These are not installed by default on SUSE LINUX, so you need to install the
libtermcap package to satisfy this dependency.
On the installation CD-ROM, the packages are located in the
/install/linux/ directory. Please read the
README file for any important last-minute information.
To install SSH Tectia Server on Linux, do the following:
- (Not necessary in "third-digit" maintenance updates.) Copy the license file as instructed in Section Licensing.
- (If installing from CD-ROM.) Copy the installation package to your machine.
- Install the package with root privileges:
# rpm -Uvh ssh-<v>.<arch>.rpm
In the command,
<v> is the current package version of SSH Tectia Server (for example,
<arch> is the platform architecture (
- 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/init.d/sshd2 restart
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
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 (