Installing on Linux

Use these instructions when you are installing Tectia Server on Linux versions running on the 32-bit x86 and the 64-bit x86-64 platform architecture.

Tectia Server for Linux platforms is supplied in RPM (Red Hat Package Manager) binary packages for Red Hat Enterprise Linux and SUSE Linux. There are separate packages for Linux versions running on the 32-bit and the 64-bit architecture.

The downloaded installation package contains the RPM installation files.

Two packages are always 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 Linux, follow the instructions below:

If installing on RHEL 8, install prerequisite packages:
```
# yum install ncurses-compat-libs
```
If installing on SuSE, install prerequisite packages:
```
# zypper install libncurses5
# zypper install insserv-compat
```
Unpack the downloaded tar package.
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 Linux version.
When installing on SUSE or Red Hat Enterprise Linux running on the 32-bit x86 architecture, use the following packages:
```
ssh-tectia-common-<version>-linux-x86.rpm
ssh-tectia-server-<version>-linux-x86.rpm
```
When installing on SUSE or Red Hat Enterprise Linux versions running on the 64-bit x86-64 architecture, use the following packages:
```
ssh-tectia-common-<version>-linux-x86_64.rpm
ssh-tectia-server-<version>-linux-x86_64.rpm
```
In the commands, <version> indicates the product release version and the current build number (for example, 6.5.2.123).
Install the packages with root privileges. In the command examples below, we use the x86 version:
```
# rpm -Uvh ssh-tectia-common-<version>-linux-x86.rpm
# rpm -Uvh ssh-tectia-server-<version>-linux-x86.rpm
```
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/licenses directory. (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.

Note

	Note
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 manually after correcting the problem. On Linux with systemd: # systemctl start ssh-server-g3 On Linux without systemd: # /etc/init.d/ssh-server-g3 start On SELinux-enabled systems, also ensure that the `semanage` command is available. In older Linux versions `semanage` is typically installed via `policycoreutils-python-utils` or `policycoreutils`.

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 manually after correcting the problem.

On Linux with systemd:
```
# systemctl start ssh-server-g3
```
On Linux without systemd:
```
# /etc/init.d/ssh-server-g3 start
```

On SELinux-enabled systems, also ensure that the semanage command is available. In older Linux versions semanage is typically installed via policycoreutils-python-utils or policycoreutils.