Differences
This shows you the differences between the selected revisions of the page.
| ftps 2016-10-16 | ftps 2024-09-18 (current) | ||
| Line 1: | Line 1: | ||
| ====== FTPS ====== | ====== FTPS ====== | ||
| - | 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 [[tls|Transport Layer Security]] (TLS) and the Secure Sockets Layer (SSL) cryptographic protocols.·((&wikipedia_ref(FTPS|FTPS))) | + | 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 [[tls|Transport Layer Security]] (TLS) cryptographic protocol (previously known as the Secure Sockets Layer – SSL).((&wikipedia_ref(FTPS|FTPS))) |
| ===== [[methods]] Methods of Invoking ===== | ===== [[methods]] 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 later method is an incompatible method that requires clients to be %%FTPS%% aware. WinSCP supports both methods. | + | 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 is an incompatible method that requires clients to be %%FTPS%% aware. WinSCP supports both methods. |
| - | __Underlined Text__==== 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. | 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. | ||
| - | __====== UHCD KICAJ GF ====== | ||
| - | ==== == Level 3 GYCDA == | ||
| - | ==== | ||
| - | __5DH DJVHDV5 SDUFA9OKLV[[HV FVVJU__[[GASDASCIK]] - GHSCA OREFAEDXA | ||
| - | __]] | ||
| ==== Implicit ==== | ==== Implicit ==== | ||