2016-11-15 17:44:58 -05:00
|
|
|
Long: cacert
|
2017-08-14 10:13:32 -04:00
|
|
|
Arg: <file>
|
2016-11-15 17:44:58 -05:00
|
|
|
Help: CA certificate to verify peer against
|
|
|
|
|
Protocols: TLS
|
|
|
|
|
---
|
|
|
|
|
Tells curl to use the specified certificate file to verify the peer. The file
|
|
|
|
|
may contain multiple CA certificates. The certificate(s) must be in PEM
|
|
|
|
|
format. Normally curl is built to use a default file for this, so this option
|
|
|
|
|
is typically used to alter that default file.
|
|
|
|
|
|
|
|
|
|
curl recognizes the environment variable named 'CURL_CA_BUNDLE' if it is
|
|
|
|
|
set, and uses the given path as a path to a CA cert bundle. This option
|
|
|
|
|
overrides that variable.
|
|
|
|
|
|
|
|
|
|
The windows version of curl will automatically look for a CA certs file named
|
|
|
|
|
\'curl-ca-bundle.crt\', either in the same directory as curl.exe, or in the
|
|
|
|
|
Current Working Directory, or in any folder along your PATH.
|
|
|
|
|
|
|
|
|
|
If curl is built against the NSS SSL library, the NSS PEM PKCS#11 module
|
|
|
|
|
(libnsspem.so) needs to be available for this option to work properly.
|
|
|
|
|
|
|
|
|
|
(iOS and macOS only) If curl is built against Secure Transport, then this
|
|
|
|
|
option is supported for backward compatibility with other SSL engines, but it
|
|
|
|
|
should not be set. If the option is not set, then curl will use the
|
|
|
|
|
certificates in the system and user Keychain to verify the peer, which is the
|
|
|
|
|
preferred method of verifying the peer's certificate chain.
|
|
|
|
|
|
2019-01-29 04:09:29 -05:00
|
|
|
(Schannel only) This option is supported for Schannel in Windows 7 or later with
|
|
|
|
|
libcurl 7.60 or later. This option is supported for backward compatibility
|
|
|
|
|
with other SSL engines; instead it is recommended to use Windows' store of
|
|
|
|
|
root certificates (the default for Schannel).
|
schannel: add support for CURLOPT_CAINFO
- Move verify_certificate functionality in schannel.c into a new
file called schannel_verify.c. Additionally, some structure defintions
from schannel.c have been moved to schannel.h to allow them to be
used in schannel_verify.c.
- Make verify_certificate functionality for Schannel available on
all versions of Windows instead of just Windows CE. verify_certificate
will be invoked on Windows CE or when the user specifies
CURLOPT_CAINFO and CURLOPT_SSL_VERIFYPEER.
- In verify_certificate, create a custom certificate chain engine that
exclusively trusts the certificate store backed by the CURLOPT_CAINFO
file.
- doc updates of --cacert/CAINFO support for schannel
- Use CERT_NAME_SEARCH_ALL_NAMES_FLAG when invoking CertGetNameString
when available. This implements a TODO in schannel.c to improve
handling of multiple SANs in a certificate. In particular, all SANs
will now be searched instead of just the first name.
- Update tool_operate.c to not search for the curl-ca-bundle.crt file
when using Schannel to maintain backward compatibility. Previously,
any curl-ca-bundle.crt file found in that search would have been
ignored by Schannel. But, with CAINFO support, the file found by
that search would have been used as the certificate store and
could cause issues for any users that have curl-ca-bundle.crt in
the search path.
- Update url.c to not set the build time CURL_CA_BUNDLE if the selected
SSL backend is Schannel. We allow setting CA location for schannel
only when explicitly specified by the user via CURLOPT_CAINFO /
--cacert.
- Add new test cases 3000 and 3001. These test cases check that the first
and last SAN, respectively, matches the connection hostname. New test
certificates have been added for these cases. For 3000, the certificate
prefix is Server-localhost-firstSAN and for 3001, the certificate
prefix is Server-localhost-secondSAN.
- Remove TODO 15.2 (Add support for custom server certificate
validation), this commit addresses it.
Closes https://github.com/curl/curl/pull/1325
2017-03-10 15:27:30 -05:00
|
|
|
|
2016-11-15 17:44:58 -05:00
|
|
|
If this option is used several times, the last one will be used.
|