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

Tectia

File Locations on Unix

On Unix platforms, the Tectia Client files are located in the following directories:

  • /etc/ssh2

    • /etc/ssh2/ssh-broker-config.xml: the global Connection Broker configuration file (see ssh-broker-config(5))

    • /etc/ssh2/ssh-broker-config-example.xml: a sample file with Connection Broker configuration examples

    • /etc/ssh2/licenses: the license file directory (see Licensing).

    • /etc/ssh2/hostkeys: the global directory for known remote host keys

  • /opt/tectia/share/auxdata/ssh-broker-ng: the Connection Broker configuration file DTD directory

    • /opt/tectia/share/auxdata/ssh-broker-ng/ssh-broker-ng-config-1.dtd: the document type definition (DTD) used with the Connection Broker configuration files. Do not edit this file!

    • /opt/tectia/share/auxdata/ssh-broker-ng/ssh-broker-config-default.xml: this configuration file is read first, and it holds the factory default settings. Do not edit this file, but you can use it to view the default settings. This file must be available and correctly formatted for the Connection Broker to start. For the configuration options, see ssh-broker-config(5).

  • /opt/tectia/bin: user binaries such as sshg3 and ssh-broker-g3

  • /opt/tectia/man: the manual pages

  • /opt/tectia/libexec: library binaries

  • /opt/tectia/lib/sshsecsh: library binaries

The user-specific configurations are stored in the following directories:

  • $HOME/.ssh2/ssh-broker-config.xml: the user-specific Connection Broker configuration file

  • $HOME/.ssh2: the default directory for user keys

    • $HOME/.ssh2/random_seed: the seed file for the random number generator

    • $HOME/.ssh2/hostkeys: the user-specific directory for known remote host keys

    • $HOME/.ssh2/identification: (optional) the identification file used with public-key authentication


 

 
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