Your FTP Today FTP site is flexible and compatible with respect to preferred file transfer protocols because we use RFC-compliant FTP server application software. Your users may connect to your FTP site via:
The standard File Transfer Protocol. FTP can be run in either active or passive mode, which determine how the data connection is established. Passive FTP is the most commmon, as this is firewall friendly to the client’s network.
FTPS & FTPeS with SSL encryption
Commonly referred to as FTP/SSL, FTPS is a name used to encompass a number of ways in which FTP client and server software can perform secure file transfers. Each way involves the use of an SSL/TLS layer below the standard FTP protocol to encrypt the control and/or data channels.
Do I need FTPS?
This feature is for those users that need SSL-secure connections while using third-party FTP client software. Often these users also wish to automate transfers and that is where the third party software comes in.
Is FTP Today’s FTPS implementation compatible with all FTPS client software?
Our implementation is fully TLS/SSL compliant, so it is compatible with any software that is also compliant (designed and coded to RFC specifications). There are also different methods of FTPS configuration. The most common methodologies of applying FTP and SSL are:
- AUTH TLS – Explicit FTPS or FTPES, named for the command issued to indicate that TLS (Transport Layer Security) should be used on port 21. This is the preferred method according to RFC 4217. The client connects to the server, but requests that TLS be used and performs the appropriate handshake before sending any sensitive data (username, password and data files).
- AUTH – Implicit FTPS – uses port 990 as defined in RFC 2228.
SFTP with SSH encryption
The SFTP protocol is used by many Unix/Linux systems as a secure alternative to FTP and is also used by certain Windows software such as SecureFX or WinSCP.
Do I need SFTP?
Some of your Unix clients may simply require you to have SFTP support. One advantage of SFTP (using SSH2) over FTPS (using SSL) is that SFTP only requires port 22 open for login and transfer, whereas FTPS uses multiple open ports. This could be a better choice if the user is behind a firewall.
Does FTP Today’s SFTP server keep users jailed?
Most FTP hosts offer SFTP only for the site administrator account and use an open source SFTP server application that allows any user to see all folders in the entire file system.
FTP Today’s SFTP implementation allows you to maintain the same jailed, multi-user experience (secure file and folder access) regardless of which file transfer protocol is used. Not only does this apply to FTP and FTPS connections, but it also applys to SFTP connections — AN INDUSTRY EXCLUSIVE!
Another fault of most competitive SFTP implementation is that there are no activity logs for SFTP transfers (typical of OpenSSH deployments). FTP Today’s SFTP implementation provides the same detailed audit reports and server logs for FTP, FTPS and SFTP transfer sessions, including reports indicating which protocol was used at the time of each activity.
FTP-over-HTTPS (our Secure Web FTP Client with SSL encryption).
This version of our Web FTP Client replaces our Standard browser-based file transfer client with our Secure file transfer client. The Secure version creates a secure HTTPS tunnel with up to 2048-bit encryption between the browser and the server. This SSL-encrypted tunnel protects all data in transit and, due to using the standard port 443 for HTTPS, is also firewall-friendly.