Enterprise with Hosted~FTP~

What is FTPS?

FTP over SSL (FTPS) connections require username/password credentials and certificate authentication. The certificate is authenticated if it was signed by a certificate authority (CA) or if the certificate was self-signed by your affiliate and you stored the copy. To authenticate a certificate, follow the guide: here. To connect to your Hosted~FTP~ account using FTPS, find out what ports, hostnames, etc. to input: here.

What is SFTP?

SFTP uses only one connection and encrypts both authentication information and data files being transferred. SSH file transfer protocol (SFTP) provides two methods for authenticating. You can use just username and password, however, with SFTP the credentials are encrypted. The other authentication method you can use with SFTP is SSH keys. This requires generating an SSH private key and public key. You then send your SSH public key to your affiliates and they load it and associate it with your account. When they connect to your SFTP server, they will transmit your public key to the server for authentication. If the public key matches your private key, along with any user or password supplied, then the authentication will succeed. Hosted~FTP~’s RSA/DSA Host Keys: Here Generating your own SSH key pairs: Here Connecting using ports, hostnames, etc. find out more: Here


One major difference between FTPS and SFTP is that FTPS uses multiple port numbers. The first port for the command channel is used for authentication and passing commands. However, every time a file transfer request or directory listing request is made, another port number needs to be opened for the data channel. You and clients/etc. have to open a range of ports in your firewalls to allow for FTPS connections, which can be a security risk for your network. SFTP needs only a single port number for all SFTP communications, making it easy to secure. Connecting using ports, hostnames, etc. find out more: Here