Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

SSH

FTP-SFTP Conversion

FTP-SFTP conversion is implemented using the Tectia SOCKS Proxy component. Tectia SOCKS Proxy acts as a SOCKS proxy for the FTP client application on the Tectia Server for IBM z/OS host and captures FTP connections based on filter rules. FTP connections are converted to SFTP, transparently to the user and to the FTP application. The only change needed in the FTP application is to change the SOCKS proxy setting to point to a localhost listener.

The SOCKS Proxy uses the host name, user name, and password information provided by the FTP client application to open an authenticated and encrypted SFTP connection to a Secure Shell SFTP server.

The Secure Shell SFTP server can also be defined in the filter rules. This way, the client's request for the FTP server destination can be overridden.

The principle of FTP-SFTP conversion is shown in Figure 8.2. Before starting the conversion, the Tectia SOCKS Proxy must be running and listening on the SOCKS port 1080 on the File Transfer Client host.

The architecture of FTP-SFTP conversion

Figure 8.2. The architecture of FTP-SFTP conversion

The following steps happen during the FTP-SFTP conversion:

  1. An application, a script, or a user triggers a file transfer.

  2. The original FTP client in the File Transfer Client host starts opening a file transfer connection to the original destination FTP server (in File Transfer Server).

  3. The FTP client makes a SOCKS query. The SOCKS setting in the FTP client is set to point to the localhost Tectia SOCKS Proxy instead of a real firewall.

  4. The filter rules that specify which connections to capture are defined in the SOCKS Proxy configuration. Connections can be captured based on the destination address and/or port.

  5. The FTP-SFTP conversion module can extract the user name, password, and the destination host name from the secured FTP application, and use them for authentication and connection setup with the Secure Shell SFTP server.

  6. The FTP-SFTP conversion module manages the FTP connection so that it remains unchanged from the original FTP client's point of view. FTP is converted to secure SFTP file transfer.

  7. The SFTP connection is managed by the Connection Broker module.

  8. The Secure Shell SFTP server in the File Transfer Server host is the end point of the file transfer.

    The unsecured original FTP server program can be eliminated from the server host.

===AUTO_SCHEMA_MARKUP===