Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ssl-reqd.d: clarify that this is for upgrading connections only #10093

Closed
wants to merge 2 commits into from
Closed

ssl-reqd.d: clarify that this is for upgrading connections only #10093

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9742415
ssl-reqd.d: clarify that this is for upgrading connections only
bagder Dec 14, 2022
4996c76
fixup language
bagder Dec 15, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/cmdline-opts/ssl-reqd.d
View file
Open in desktop
Expand Up @@ -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.