Jump to content

FTPS

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Typhoonhurricane (talk | contribs) at 17:21, 17 February 2010 (→Explicit). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

This article is about FTP over SSL. For FTP Software, the defunct network software company, see FTP Software.

FTPS (also known as FTP Secure and FTP-SSL) is an extension to the commonly used File Transfer Protocol (FTP) that adds support for the Transport Layer Security (TLS) and the Secure Sockets Layer (SSL) cryptographic protocols.

FTPS should not be confused with the SSH File Transfer Protocol (SFTP), an incompatible secure file transfer subsystem for the Secure Shell (SSH) protocol. It is also different from Secure FTP, the practice of tunneling FTP through an SSH connection.

Background

The File Transfer Protocol was drafted in 1971 [1] for use with the scientific and research network, ARPANET. Access to the ARPANET during this time was limited to a small number of military sites and universities, negating the need for data security or privacy requirements within the protocol.

As the ARPANET gave way to the Internet, data began to traverse increasingly longer paths from client to server. The opportunity for unauthorized third parties to eavesdrop on data transmissions proportionally increased.

In 1994, the Internet browser company Netscape developed and released the application layer wrapper, Secure Sockets Layer. [2] This protocol enables applications to communicate across a network in a private and secure fashion, discouraging eavesdropping, tampering, and message forgery. While it can add security to any protocol that uses reliable connections (such as TCP), it was most commonly used by Netscape with HTTP to form HTTPS.

The SSL protocol was eventually applied to FTP, with a draft Request for Comments (RFC) published in late 1996. [3] An official IANA port was registered shortly thereafter. However, the RFC was not finalized until 2005. [4]

Methods of invoking

Two separate methods were developed to invoke client security for use with FTP clients: Explicit or Implicit. The former method is a legacy compatible implementation where FTPS aware clients can invoke security with an FTPS aware server without breaking overall FTP functionality with non-FTPS aware clients. The latter method requires clients to be FTPS aware, and thus is incompatible with non-FTPS-aware clients.

Explicit

In explicit mode (also known as FTPES), an FTPS client must "explicitly request" security from an FTPS server and then step-up to a mutually agreed encryption method. If a client does not request security, the FTPS server can either allow the client to continue insecure or refuse/limit the connection.

The mechanism for negotiating authentication and security with FTP was added under RFC 2228, which included the new FTP command AUTH. While this RFC does not explicitly define any required security mechanisms (ie, SSL or TLS), it does require that the FTPS client will challenge the FTPS server with a mutually known mechanism. If the FTPS client challenges the FTPS server with an unknown security mechanism, the FTPS server will respond to the AUTH command with error code 504 (not supported). Clients could determine which mechanisms were supported by querying the FTPS server with the FEAT command, although it should be noted that servers are not necessarily required to be honest in disclosing what levels of security they support. Common methods of invoking FTPS security included: AUTH TLS and AUTH SSL.

In the later RFC 4217, FTPS compliance required that clients always negotiate using the AUTH TLS method. The RFC also recommends FTPS servers to accept the draft mechanism AUTH TLS-C.

Implicit

Negotiation is not allowed with implicit FTPS configurations. A client is immediately expected to challenge the FTPS server with a TLS/SSL ClientHello message. If such a message is not received by the FTPS server, the server should drop the connection.

In order to maintain compatibility with existing non-TLS/SSL aware FTP clients, implicit FTPS was expected to listen on the IANA Well Known Port 990/TCP for the FTPS control channel and 989/TCP for the FTPS data channel. This allowed administrators to retain legacy compatible services on the original 21/TCP FTP control channel.

Note that implicit negotiation was not defined in RFC 4217. As such, it is considered an earlier, deprecated method of negotiating TLS/SSL for FTP.

TLS/SSL

Main article: Transport Layer Security

General support

FTPS includes full support for the TLS and SSL cryptographic protocols, including the use of server-side public key authentication certificates and client-side authorization certificates. It also supports compatible ciphers, including AES, RC4, RC2, Triple DES and DES, and hash functions SHA, MD5, MD4 and MD2.

Scope of use

In Implicit Mode, the entire FTPS session is encrypted. However, Explicit Mode differs in that the client has full control over what areas of the connection are to be encrypted. Enabling and disabling of encryption for the FTPS control channel and FTPS data channel can occur at any time. The only restriction comes from the FTPS server, which has the ability to deny commands based on server encryption policy.

Secure command channel

The secure command channel mode can be entered through the issue of either the AUTH TLS or AUTH SSL commands. After such time, all command control between the FTPS client and server are assumed to be encrypted. It is generally advised to enter such a state prior to user authentication and authorization in order to avoid the eavesdropping of user name and password data by third parties.

The FTPS client may exit the secure command channel mode at any time by issuing a CCC (clear control channel) command. It may be reentered again later by issuing another AUTH command.

Secure data channel

The secure data channel can be entered through the issue of the PROT command. It is not enabled by default when the AUTH TLS command is issued. After such time, all data channel communication between the FTPS client and server is assumed to be encrypted.

The FTPS client may exit the secure data channel mode at any time by issuing a CDC (clear data channel) command. (this command is not specified in RFC4217, RFC2228 or RFC959 - where is it specified?)

Reasons to disable encryption

It may not be advantageous to use data channel encryption when performing transfers under the following scenarios:

  • Files being transferred are of a non-sensitive nature, making encryption unnecessary
  • Files being transferred are already encrypted at the file level, making encryption redundant
  • Available TLS or SSL encryption modes do not meet desired level of encryption. This is common with older FTPS clients or servers that may have been limited to 40-bit SSL due to previous United States high-encryption export laws.

It may not be advantageous to use control channel encryption under the following scenarios:

  • Use of FTPS when the client and/or server resides behind a network firewall or network address translation (NAT) device. (See Firewall Incompatibilities below)
  • Repeated use of AUTH and CCC/CDC commands by anonymous FTP clients within the same session. Such behavior can be utilized as a resource-based denial of service attack as the TLS/SSL session must be regenerated each time, utilizing server processor time.

SSL certificates

Much like HTTPS, but unlike SFTP, FTPS servers may provide a public key certificate. These certificates can be created using Unix tools such as OpenSSL's ssl-ca.

This certificate should be signed by a certificate authority, or the FTPS client may generate a warning stating that the certificate is not valid.

Firewall incompatibilities

Because FTP utilizes a dynamic secondary port (for data channels), many firewalls were designed to snoop FTP protocol control messages in order to determine what secondary data connections they need to allow. However, if the FTP control connection is encrypted using TLS/SSL, the firewall cannot determine the TCP port number of a data connection negotiated between the client and FTP server.

Therefore, in many firewalled networks, an FTPS deployment will fail when an unencrypted FTP deployment will work, but this problem can be solved with the use of a limited range of ports for data and configuring the firewall to open these ports.

See also

References

  1. ^ RFC-265: File Transfer Protocol (FTP)
  2. ^ RFC draft, SSL 2.0 Protocol Specification, revision 1995-02-09
  3. ^ RFC draft, Secure FTP Over SSL, revision 1996-11-26
  4. ^ RFC-4217: Securing FTP with TLS
Retrieved from "https://en.wikipedia.org/w/index.php?title=FTPS&oldid=344645741"