From 50750d097aa55864498d2622fd14aad17fda941e Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 14 Dec 2022 13:56:42 +0100 Subject: [PATCH] ssl-reqd.d: clarify that this is for upgrading connections only Closes #10093 --- docs/cmdline-opts/ssl-reqd.d | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/cmdline-opts/ssl-reqd.d b/docs/cmdline-opts/ssl-reqd.d index cf81fb2291..6f95d5b672 100644 --- a/docs/cmdline-opts/ssl-reqd.d +++ b/docs/cmdline-opts/ssl-reqd.d @@ -9,11 +9,15 @@ Example: --ssl-reqd ftp://example.com See-also: ssl insecure Multi: boolean --- -Require SSL/TLS for the connection. Terminates the connection if the server -does not support SSL/TLS. +Require SSL/TLS for the connection. Terminates the connection if the transfer +cannot be upgraded to use SSL/TLS. This option is handled in LDAP since version 7.81.0. It is fully supported by the OpenLDAP backend and rejected by the generic ldap backend if explicit TLS is required. +This option is unnecessary if you use a URL scheme that in itself implies +immediate and implicit use of TLS, like for FTPS, IMAPS, POP3S, SMTPS and +LDAPS. Such transfers will always fail if the TLS handshake does not work. + This option was formerly known as --ftp-ssl-reqd. -- 2.47.3