FTP over SSL

FTP over SSL


FTP over SSL

FTPS, which is sometimes incorrectly referred to as [Secure FTP][sftp], takes the existing [FTP protocol][ftp] and adds support for Transport Layer Security. TLS wraps the existing protocol, encrypting and securing the data in flight, and also allows for the identity of the server to be proven using SSL certificates.

FTPS can encrypt the control channel (which carries the username, password and the meta data about files), or the data channel (which carries the content of the files) or both. In iWeb FTP's case we secure both.

FTPS uses one port for inbound connections (21), and this is used for the control channel, but it can use any number of connections- in or outbound- for the data channel. This can lead to some problems when FTPS is used in environments using network address translation, especially when it is used in active mode. It's almost always a good idea to select passive mode when using FTPS.

People accessing their iWeb FTP site through the [web interface will also use SSL by default][web]

[web]: <?php echo Nz_Url::route('feature-web-access') ?> [sftp]: <?php echo Nz_Url::route('feature-secure-ftp') ?> [ftp]: <?php echo Nz_Url::route('feature-ftp-compatible') ?>