mirror of
https://github.com/curl/curl.git
synced 2024-12-27 06:59:43 +08:00
2bc1d775f5
- they are mostly pointless in all major jurisdictions - many big corporations and projects already don't use them - saves us from pointless churn - git keeps history for us - the year range is kept in COPYING checksrc is updated to allow non-year using copyright statements Closes #10205
24 lines
827 B
D
24 lines
827 B
D
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: ssl-reqd
|
|
Help: Require SSL/TLS
|
|
Protocols: FTP IMAP POP3 SMTP LDAP
|
|
Added: 7.20.0
|
|
Category: tls
|
|
Example: --ssl-reqd ftp://example.com
|
|
See-also: ssl insecure
|
|
Multi: boolean
|
|
---
|
|
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.
|