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

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server for IBM z/OS >>
    Getting Started with SSH Tectia Server for IBM z/OS >>
    Configuring the Server >>
    Authentication >>
    System Administration >>
    File Transfer Using SFTP >>
    Secure File Transfer Using Transparent FTP Security >>
        Introduction to Transparent FTP Security
        Configuring SOCKS Proxy
            ssh-socks-proxy-config.xml
            Storing Remote Server Host Keys
        Creating the SSHSP User
        Running SOCKS Proxy >>
        Configuring FTP >>
        Examples of Transparent FTP Security>>
    Tunneling >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Man Pages and Default Configuration Files >>
    Log Messages >>

Configuring SOCKS Proxy

The SSH Tectia SOCKS Proxy component used in transparent FTP tunneling and FTP-SFTP conversion does not use the regular client configuration ssh-broker-config.xml. Instead, the configuration is read from the ssh-socks-proxy-config.xml file.

Like the ssh-broker-config.xml file, the ssh-socks-proxy-config.xml file can be located in the system-wide /opt/tectia/etc directory and/or in the user-specific $HOME/.ssh2 directory.

The SOCKS Proxy reads the server host keys from the normal locations ($HOME/.ssh2 and $HOME/.ssh2/hostkeys). However, if the server authenticates itself using a certificate, the information on the CA certificate (or the server certificate) must be defined separately in the ssh-socks-proxy-config.xml file.

ssh-socks-proxy-config.xml

Storing Remote Server Host Keys

PreviousNextUp[Contents] [Index]


[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]

Copyright © 2011 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice


 

 
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