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 >>
    File Transfer Using SFTP >>
    Secure File Transfer Using Transparent FTP Security >>
        Introduction to Transparent FTP Security
        Configuring SOCKS Proxy >>
            Storing Remote Server Host Keys
        Creating the SSHSP User
        Running SOCKS Proxy >>
        Using Public-Key Authentication with the 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 >>


The ssh-socks-proxy-config.xml configuration file uses the same format as the ssh-broker-config.xml configuration file.

The /opt/tectia/etc/ssh-socks-proxy-config-example.xml configuration file provided in the installation package is shown below. The configuration tunnels all FTP connections using the hostname and username provided by the FTP client application. To enable the configuration, copy the file to /opt/tectia/etc/ssh-socks-proxy-config.xml.

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE secsh-broker SYSTEM 
 "/opt/tectia/etc/ssh-tectia/auxdata/ssh-broker-ng/ssh-broker-ng-config-1.dtd" >
<secsh-broker version="6.0" >
    <profile name="dynamic-ftp"
    <tunnel type="socks-proxy"
            profile="" />
     <rule ip-address=".*"
           fallback-to-plain="NO" />
    <log-events facility="auth" severity="informational">

You can edit the ssh-socks-proxy-config.xml configuration file using a normal text editor. The complete configuration options are described in the ssh-broker-config man page.

The following settings are required in the ssh-socks-proxy-config.xml file to enable transparent FTP tunneling or FTP-SFTP conversion:

  • profiles

    At least one profile element must be defined.

    The profile id must be a unique identifier that does not change during the lifetime of the profile.

    An additional name can be given to the profile. This is a free-form text string.

    The host attribute defines the address of the Secure Shell server host. If it is left empty and/or under the filter-engine/rule element hostname-from-app="yes", the Secure Shell connection is opened to the destination host given in the SOCKS request. Otherwise the Secure Shell connection is opened to the host specified in the profile and in FTP tunneling, FTP connections are forwarded to the requested hosts.

    The port attribute specifies the Secure Shell server port. The default port is 22.

    The user attribute specifies the username on the Secure Shell server. If it is left empty, the username given by the FTP client is used when opening the Secure Shell connection.

  • static-tunnels

    At least one tunnel element must be defined.

    For transparent tunneling, the tunnel type must be set as "socks-proxy and the port as "1080".

    The listen-address is usually the loopback address "", but can be an address of any local interface that will be listened.

    The dst-port attribute is set to 0 and the profile attribute is left empty when transparent tunneling and FTP-SFTP conversion are used.

  • filter-engine

    At least one rule element must be defined.

    The ip-address attribute specifies the target host IP address to be filtered. It can be a regular expression. Connections to the specified address are captured. With transparent FTP tunneling and FTP-SFTP conversion, this can be usually set to capture all connections (".*"), as the connections are already filtered by the SOCKS Proxy settings.

    The ports attribute specifies the ports to be filtered. It can be a single port or a range. A range is specified with a dash between two integers (such as "21-25").

    The action attribute specifies the action to be done when a filter is used. For transparent FTP tunneling, the action is "ftp-tunnel". For FTP-SFTP conversion, the action is "ftp-proxy".

    The profile-id attribute is a reference to a profile element and should contain the same value as the id attribute of the profile.

    The hostname-from-app attribute defines whether the SOCKS Proxy should extract the Secure Shell server's host name from data sent by the application, or use a Secure Shell server defined by the connection profile in profile-id. With SSH Tectia SOCKS Proxy on z/OS, this is usually set to "yes". Note that this requires that a Secure Shell server is installed to each destination server (or that fallback-to-plain is enabled to allow direct connections to those servers that do not have Secure Shell installed).

    The username-from-app attribute defines whether the FTP tunneling or FTP-SFTP conversion extracts the user name from data sent by the FTP application. With SSH Tectia SOCKS Proxy on z/OS, this is usually set to "yes". This setting will override any user name settings made in a related connection profile.

    When applying the filter rule, if creating the tunnel fails or the connection to the Secure Shell server fails, the SOCKS Proxy will normally return a "host not reachable" error. However, if the fallback-to-plain attribute is set to "yes", a direct (unsecured) connection is used instead.

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