當您正在為員工設定遠端檔案傳輸功能時，您希望事情儘可能簡單和安全。考慮到這一點，FTPS和SFTP哪個更好？今天的超級使用者問答帖子為一位好奇的讀者提供了答案。

今天的問答環節是由SuperUser提供的，SuperUser是Stack Exchange的一個分支，是一個由社群驅動的問答網站分組。

由kojihachisu（Flickr）提供的螢幕截圖。

問題

超級使用者讀者user334875想知道FTPS和SFTP之間的區別，以及哪個更好：

I am trying to set up a system for four of my employees who work remotely so that they can transfer files. I also need it to be secure. Is SFTP better than FTPS? What is the difference between the two?

兩者有什麼區別？哪一個更好？

答案

超級使用者貢獻者NuTTyX和Vdub為我們提供了答案。首先，NuTTyX：

They are two completely different protocols.

FTPS is FTP with SSL for security. It uses a control channel and opens new connecti*** for the data transfer. As it uses SSL, it requires a certificate.

SFTP (SSH File Transfer Protocol/Secure File Transfer Protocol) was designed as an extension of SSH to provide file transfer capability, so it usually uses only the SSH port for both data and control.

In most SSH server installati*** you will have SFTP support, but FTPS would need the additional configuration of a supported FTP server.

接著是Vdub的回答：

FTPS (FTP/SSL) is a name used to provide a number of ways that FTP software can perform secure file transfers. Each way involves the use of a SSL/TLS layer below the standard FTP protocol to encrypt the control and/or data channels.

Pros:

• Widely known and used
• The communication can be read and understood by a human
• Provides services for server-to-server file transfer
• SSL/TLS has good authentication mechani**s (X.509 certificate features)
• FTP and SSL/TLS support is built into many internet communicati*** frameworks

C***:

• Does not have a uniform directory listing format
• Requires a secondary DATA channel, which makes it hard to use behind firewalls
• Does not define a standard for file name character sets (encodings)
• Not all FTP servers support SSL/TLS
• Does not have a standard way to get and change file or directory attributes

SFTP (SSH File Transfer Protocol) is a network protocol that provides file transfer and manipulation functionality over any reliable data stream. It is typically used with the SSH-2 protocol (TCP port 22) to provide secure file transfer, but is intended to be usable with other protocols as well.

Pros:

• Has a good standards background which strictly defines most (if not all) aspects of operati***
• Has only one connection (no need for a DATA connection)
• The connection is always secured
• The directory listing is uniform and machine-readable
• The protocol includes operati*** for permission and attribute manipulation, file locking, and more functionality

C***:

• The communication is binary and can not be logged “as is” for human reading
• SSH keys are harder to manage and validate
• The standards define certain things as optional or recommended, which leads to certain compatibility problems between different software titles from different vendors.
• No server-to-server copy and recursive directory removal operati***
• No built-in SSH/SFTP support in VCL and .NET frameworks

有什麼要補充的解釋嗎？在評論中發出聲音。想從其他精通技術的Stack Exchange使用者那裡瞭解更多答案嗎？在這裡檢視完整的討論主題。