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

SSH

Server Authentication with Public Keys

A public key is always created for Tectia Server during the installation phase. In addition, the Server administrator can generate more public-key pairs for the host, according to need.

The server is authenticated with a digital signature based on an RSA, DSA, or ECDSA public-key algorithm. At the beginning of each connection, the server sends its public key to the client for validation.

The key pair that the server uses in server authentication is defined in the server configuration file, ssh-server-config.xml, with the following elements:

<params>
  <hostkey>      
    <private file="/etc/ssh2/hostkey" />
    <public file="/etc/ssh2/hostkey.pub" />
  </hostkey>
...
</params>

Giving the public key in the configuration file is not mandatory. It will be derived from the private key if it is not found otherwise. Specifying the public key will, however, decrease start-up time for the software, as deriving the public key is a somewhat time-consuming operation.

During the installation process, one RSA key pair (with the file names hostkey and hostkey.pub) is generated and stored in the /etc/ssh2 directory on Unix and in the "<INSTALLDIR>\SSH Tectia Server" directory on Windows. By default, this key pair is used for server authentication.

Each Tectia Server can have multiple host keys. You could have, for example, the following set of parameters in your ssh-server-config.xml file:

<params>
  <hostkey>      
    <private file="/etc/ssh2/hostkey_rsa" />
    <public file="/etc/ssh2/hostkey_rsa.pub" />
  </hostkey>

  <hostkey>      
    <private file="/etc/ssh2/hostkey_dsa" />
    <public file="/etc/ssh2/hostkey_dsa.pub" />
  </hostkey>

  <hostkey>      
    <private file="/etc/ssh2/hostkey_ecdsa" />
    <public file="/etc/ssh2/hostkey_ecdsa.pub" />
  </hostkey>
...
</params>

All keys are stored in memory when the ssh-server-g3 process is started, which means that any one of them can be used to authenticate the server.

We recommend that you use a maximum of one key pair of each type (RSA, DSA, ECDSA). If also certificates are used in server authentication, an additional three host key pairs (RSA/ DSA/ECDSA with certificate) can be used for a total of six host keys.

The host keys can be configured with the Tectia Server Configuration tool on the Identity page. See Identity.


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more