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

SSH

Files Used in This Example

The following files will be modified or, if they do not already exist, created during this example:

ssh-socks-proxy-config.xml

The Tectia SOCKS Proxy configuration file ssh-socks-proxy-config.xml will in this example be created from the example configuration file ssh-socks-proxy-config-example.xml.

<USERID>.FTP.DATA (where <USERID> is your user ID) or TCPIP.FTP.DATA

If <USERID>.FTP.DATA does not exist, FTP will default to TCPIP.FTP.DATA. If you want these settings to be used only for <USERID>, you should create and use <USERID>.FTP.DATA as shown in this example.

socks.conf

This file can be called anything and placed anywhere (including as data set) as long as <USERID>.FTP.DATA or TCPIP.FTP.DATA point to the correct file. In this example /opt/tectia/etc/socks.conf will be created and used.


 

 
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