Installing on Linux (DEB)

Tectia Server for Debian GNU/Linux platforms is supplied in Debian (DEB) binary packages for Ubuntu and Debian running on the 64-bit x86-64 architecture.

The Tectia Server installation bundle contains the DEB files and the license files for both the Tectia Server and Tectia Client that can be optionally installed on the same host.

To install Tectia Server on Debian, follow the instructions below:

  1. Make sure no other Secure Shell software is using port 22 (Tectia Server default listen port). Also make sure the firewall is open for port 22.

  2. Download the installation bundle according to your license type:

    • Commercial Tectia Quantum Safe Edition License:

    • Commercial License:

    • Evaluation:


    In the package names, <version> is the current product release (for example,

  3. Unpack the downloaded tar package.

  4. Select the installation packages (in this example, we install Tectia Server only). Two packages are always required: one for the common components of Tectia Client and Server, and one for the specific components of Tectia Server.

  5. Install the packages with root privileges:

    # dpkg -i ssh-tectia-common-<version>_linux-x86_64.deb
    # dpkg -i ssh-tectia-server-<version>_linux-x86_64.deb

    If you have already installed Tectia Client, you don't need to install the common file again.

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

  6. Copy the license file to the /etc/ssh2/licenses directory. (This is not necessary in "third-digit" maintenance updates.)

    If this is the initial installation of Tectia, 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 Tectia Server manually after copying the license file.

  7. The installation should (re)start Tectia Server automatically.

    If Tectia 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:

    # ssh-server-ctl start