|
|
||||||
|
|
Secure FTP
The intent of this article is to explain how FTPS servers, SFTP servers and HTTPS differ from one another, and the benefits or pitfalls of each method of encryption. As you will understand when you read on, FTP Today sorts through the choices for you. We have taken the strongest method of encryption (SSL) and created two ways to utilize it, one that is functional only using our Web FTP Client and one that is functional with all third party FTP client software. FTPS (FTP using SSL) Best for Secure and Automated Transfers Advantages: Disadvantages: [MINOR] FTP - over - HTTPS (SSL Tunnel) Best for Secure Web-based Transfers Advantages:
Disadvantages: [NONE]
SFTP using SSH2 A poor choice compared to SSL Some standalone FTP client software offer "SFTP". SFTP is not a generic acronym for "Secure File Transfer Protocol"; The "S" stands for encryption using Secure SSH (Secure SHell). While this is technically still 128-bit encryption, that is where the similarity to the above SSL methods ends. Disadvantages: [MAJOR]
FTP Today sees no advantages in deploying SFTP on your hosting account, therefore we do not recommend this solution except in rare cases where you are already using SFTP over SSH2 or some customer of yours forces your hand. Please contact Sales to discuss costs and deployment of SFTP in lieu of FTPS. HTTPS (HTTP using SSL) Not designed for File Transfer applications. Disadvantages: HTTPS is used in hosting websites with e-commerce applications. This is great for securing order forms while customers enter credit cards, but functions like user-authentication and folder privacy are not best handled by HTTP or HTTPS. The HTTPS protocol is not natively meant for transferring files. It is meant for displaying web content over a secure connection from a web browser to a web server. |
|||||