Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia

Installing on Linux

SSH 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 x86 and the 64-bit x86-64 platform architecture.

The downloaded online installation package contains the RPM installation files. On the installation CD-ROM, the installation packages for Linux are located in the /install/linux/ directory.

Two packages are required: one for the common components of SSH Tectia Client and Server, and another for the specific components of SSH Tectia Server.

To install SSH Tectia Server on Linux, follow the instructions below:

  1. Make sure no other Secure Shell software is using port 22 (SSH Tectia Server default listen port). Stop any competing server software or change their listen port.

  2. Select the installation package according to your Linux version.

    When installing on Linux running on the 32-bit x86 architecture, select the following packages:

    ssh-tectia-common-<ver>.i386.rpm
    ssh-tectia-server-<ver>.i386.rpm 
    

    When installing on Linux running on the 64-bit x86-64 architecture, select the following packages:

    ssh-tectia-common-<ver>.x86_64.rpm
    ssh-tectia-server-<ver>.x86_64.rpm
    

    In the commands, <ver> is the current package version of SSH Tectia Server (for example, 5.3.8.123).

  3. Install the packages with root privileges:

    # rpm -Uvh ssh-tectia-common-<ver>.<arch>.rpm
    # rpm -Uvh ssh-tectia-server-<ver>.<arch>.rpm
    

    In the commands, <arch> is the platform architecture i386 or x86_64.

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

  4. (Not necessary in "third-digit" maintenance updates.) Copy the license file to the /etc/ssh2/licenses directory. See Licensing.

    If this is the initial installation of SSH 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.

  5. 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 after correcting the problem by issuing the command:

    # /etc/init.d/ssh-server-g3 start
    


 

 
PrivX
 

 

 
What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.



    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH



    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now