Tools
Serv-U to Serv-U Gateway connection security
This article describes the security configurations and protocols used by Serv-U and the Serv-U Gateway connections.
First published date
Last published date
Overview
This article describes the security configurations and protocols used by Serv-U and the Serv-U Gateway connections.
Note: See the Serv-U Distributed Architecture Guide for information about the purpose and timing of these connections.
Product section
Resolution
Serv-U connects to Serv-U Gateway using multiple connections to send configuration data, listen for new connections, and transfer files. Serv-U to Serv-U Gateway connections are encrypted as long as the related listener's protocol is a secure protocol (such as FTPS, SFTP, or HTTPS).
Gateway control channel
Gateway data channel Serv-U uses connections to control and monitor the Serv-U Gateway. These connections are implemented as proprietary TCP/IP connections.
The Serv-U to Serv-U Gateway connections that handle FTPS and HTTPS connections are protected by SSL/TLS. As a result:All data connections used between Serv-U and Serv-U Gateway use the same protection mechanism as the related listener on Serv-U Gateway.
- SFTP connections are protected by SSH.
- FTP and HTTP connections are not protected because they use clear text.
The same certificate key lengths and negotiated bit strength apply to the Serv-U to Serv-U Gateway connections.