1=pod
2
3=head1 NAME
4
5SSL_CTX_load_verify_locations - set default locations for trusted CA
6certificates
7
8=head1 SYNOPSIS
--- 19 unchanged lines hidden (view full) ---
28 -----END CERTIFICATE-----
29
30sequences. Before, between, and after the certificates text is allowed
31which can be used e.g. for descriptions of the certificates.
32
33The B<CAfile> is processed on execution of the SSL_CTX_load_verify_locations()
34function.
35
36If on an TLS/SSL server no special setting is performed using *client_CA_list()
37functions, the certificates contained in B<CAfile> are listed to the client
38as available CAs during the TLS/SSL handshake.
39
40If B<CApath> is not NULL, it points to a directory containing CA certificates
41in PEM format. The files each contain one CA certificate. The files are
42looked up by the CA subject name hash value, which must hence be available.
43If more than one CA certificate with the same name hash value exist, the
44extension must be different (e.g. 9d66eef0.0, 9d66eef0.1 etc). The search
45is performed in the ordering of the extension number, regardless of other
46properties of the certificates.
47Use the B<c_rehash> utility to create the necessary links.
48
49The certificates in B<CApath> are only looked up when required, e.g. when
50building the certificate chain or when actually performing the verification
51of a peer certificate.
52
53On a server, the certificates in B<CApath> are not listed as available
54CA certificates to a client during a TLS/SSL handshake.
55
56When looking up CA certificates, the OpenSSL library will first search the
57certificates in B<CAfile>, then those in B<CApath>. Certificate matching
58is done based on the subject name, the key identifier (if present), and the
59serial number as taken from the certificate to be verified. If these data
60do not match, the next certificate will be tried. If a first certificate
61matching the parameters is found, the verification process will be performed;
62no other certificates for the same parameters will be searched in case of
63failure.
64
65When building its own certificate chain, an OpenSSL client/server will
66try to fill in missing certificates from B<CAfile>/B<CApath>, if the
67certificate chain was not explicitly specified (see
68L<SSL_CTX_add_extra_chain_cert(3)|SSL_CTX_add_extra_chain_cert(3)>,
69L<SSL_CTX_use_certificate(3)|SSL_CTX_use_certificate(3)>.
70
71=head1 WARNINGS
72
--- 52 unchanged lines hidden ---
2
3=head1 NAME
4
5SSL_CTX_load_verify_locations - set default locations for trusted CA
6certificates
7
8=head1 SYNOPSIS
--- 19 unchanged lines hidden (view full) ---
28 -----END CERTIFICATE-----
29
30sequences. Before, between, and after the certificates text is allowed
31which can be used e.g. for descriptions of the certificates.
32
33The B<CAfile> is processed on execution of the SSL_CTX_load_verify_locations()
34function.
35
36If on an TLS/SSL server no special setting is performed using *client_CA_list()
37functions, the certificates contained in B<CAfile> are listed to the client
38as available CAs during the TLS/SSL handshake.
39
40If B<CApath> is not NULL, it points to a directory containing CA certificates
41in PEM format. The files each contain one CA certificate. The files are
42looked up by the CA subject name hash value, which must hence be available.
43If more than one CA certificate with the same name hash value exist, the
44extension must be different (e.g. 9d66eef0.0, 9d66eef0.1 etc). The search
45is performed in the ordering of the extension number, regardless of other
46properties of the certificates.
47Use the B<c_rehash> utility to create the necessary links.
48
49The certificates in B<CApath> are only looked up when required, e.g. when
50building the certificate chain or when actually performing the verification
51of a peer certificate.
52
53On a server, the certificates in B<CApath> are not listed as available
54CA certificates to a client during a TLS/SSL handshake.
55
56When looking up CA certificates, the OpenSSL library will first search the
57certificates in B<CAfile>, then those in B<CApath>. Certificate matching
58is done based on the subject name, the key identifier (if present), and the
59serial number as taken from the certificate to be verified. If these data
60do not match, the next certificate will be tried. If a first certificate
61matching the parameters is found, the verification process will be performed;
62no other certificates for the same parameters will be searched in case of
63failure.
64
65When building its own certificate chain, an OpenSSL client/server will
66try to fill in missing certificates from B<CAfile>/B<CApath>, if the
67certificate chain was not explicitly specified (see
68L<SSL_CTX_add_extra_chain_cert(3)|SSL_CTX_add_extra_chain_cert(3)>,
69L<SSL_CTX_use_certificate(3)|SSL_CTX_use_certificate(3)>.
70
71=head1 WARNINGS
72
--- 52 unchanged lines hidden ---