Differences
This shows you the differences between the selected revisions of the page.
| 2019-02-26 | 2019-12-03 | ||
| Restored revision 1547865470. Undoing revision 1551184283. (martin) (hidden) | no summary (91.137.135.89) (hidden) (untrusted) | ||
| Line 5: | Line 5: | ||
| 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. | 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. | ||
| - | ==== Explicit ==== | + | ==== Explicit ALMA0110 ==== |
| 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. | ||