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

SSH

Client Configuration Files

The following files located in the /opt/tectia/etc directory are used to store the client configuration information:

  • /opt/tectia/etc/ssh-broker-config.xml: the global Connection Broker configuration file

  • /opt/tectia/etc/ssh_ftadv_config: the global file transfer advisor profile configuration file

  • /opt/tectia/etc/ssh-socks-proxy-config.xml: the global SOCKS Proxy configuration file

  • /opt/tectia/etc/hostkeys: the global directory for known remote server host keys

The user-specific configurations are stored in each user's $HOME/.ssh2 directory:

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

  • $HOME/.ssh2/ssh_ftadv_config: the user-specific file transfer advisor profile configuration file

  • $HOME/.ssh2/ssh-socks-proxy-config.xml: the user-specific SOCKS Proxy configuration file

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

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

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


 

 
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