Installing IBM Global Security Kit packages

How you install the IBM® Global Security Kit (GSKit) packages depends on the Linux system that you are running.

About this task

If you plan to install IBM Global Security Kit (GSKit) on a non-Debian Linux system, use the rpm command. You can install the package in either the default location or one of your choosing.

If you plan to install IBM Global Security Kit (GSKit) on a Debian Linux system, such as Ubuntu, you have the option of forcing the rpm installation, or converting the package into a Debian format and installing the converted package.

Note: While Debian Linux systems support rpm command installations, Debian packaging is preferred.

Procedure

Use one of the following methods to install IBM Global Security Kit (GSKit) on your Linux system:

For non-Debian system installations to the default location:

To install IBM Global Security Kit (GSKit) packages to the default location,/usr/local, run the command rpm -Uv GSKit_Crypt_RPM GSKit_SSL_RPM

For example:

rpm -Uv gskcrypt32-8.0.14.8.linux.x86_64 \
		gskssl32-8.0.14.8.linux.x86_64.rpm

For non-Debian system installations to a location of your choosing:

To install IBM Global Security Kit (GSKit) packages to a location that you specify, run the command

rpm -Uv
--prefix new_location rpm_file

To avoid the errors of the post-install script, which occur if you do not have root authority, use the --noscripts flag:

rpm -Uv --prefix new_location rpm_file --noscripts

For Debian system installations using the rpm command:

Because Debian packaging is preferred on Debian Linux systems, the rpm database on a new Debian Linux system might not be populated, causing an rpm installation to fail the prerequisite checking.

To install IBM Global Security Kit (GSKit) packages by using the rpm command, include the --nodeps flag in your installation statement to force the installation. The Debian Linux system warns you that the rpm command should not be used, but you can suppress this prompt by adding the --force-debian flag to your installation statement.

rpm -Uh gskcrypt64-8.0.55.4.linux.x86_64.rpm --nodeps --force-debian

For Debian system installations using native Debian packaging:

Convert the IBM Global Security Kit (GSKit) rpm package to Debian packaging by using the alien tool:
```
alien gskssl64-8.0.54.4.linux.x86_64.rpm --target x86_64 --keep-version --scripts
```
Install the converted package:
```
dpkg -i gskssl64_8.0-55.4_x86_64.deb
```

To see what IBM Global Security Kit (GSKit) level is installed when using this method, use the apt tool:

dpkg -l | grep gsk

Note: Although the IBM Global Security Kit (GSKit) Transport Layer Security (TLS) package has a dependency on the IBM Global Security Kit (GSKit) Crypto package, the Debian installation method does not check this at install time. Ensure that the IBM Global Security Kit (GSKit) TLS package and IBM Global Security Kit (GSKit) Crypto package are both installed at the same build level.

Also, RPM and Debian installation databases are not aware of each other, so it is possible for one installation to back-level another. For example, you can install IBM Global Security Kit (GSKit) 8.0.50.30 with rpm but then install IBM Global Security Kit (GSKit) 8.0.50.10 with dbpkg, which overwrites the newer installation with an older one.