Differences
This shows you the differences between the selected revisions of the page.
| 2009-03-01 | 2009-03-04 | ||
| created (martin) | control and data channel encryption (martin) | ||
| Line 7: | Line 7: | ||
| ==== Explicit ==== | ==== Explicit ==== | ||
| In explicit mode, a FTPS client must "explicitly request" security from a 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. | In explicit mode, a FTPS client must "explicitly request" security from a 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. | ||
| + | |||
| + | In Explicit Mode, 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. WinSCP though requests encryption for both control and data channel unconditionally during whole session. | ||
| ==== Implicit ==== | ==== Implicit ==== | ||
| - | Negotiation is not allowed with implicit FTPS configurations. A client is immediately expected to challenge the FTPS server with a connection ecrypter using TLS/SSL. If it does not, the server should drop the connection. | + | Negotiation is not allowed with implicit FTPS configurations. A client is immediately expected to challenge the FTPS server with a connection ecrypted using TLS/SSL. If it does not, 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. | 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. | ||
| + | |||
| + | In Implicit Mode, the entire FTPS session (both control and data channels) is unconditionally encrypted. | ||
| ===== SSL Certificates ===== | ===== SSL Certificates ===== | ||