#include
int SSL_CTX_load_verify_locations(SSL_CTX *ctx, const char *CAfile, const char *CApath);
-----BEGIN CERTIFICATE----- ... (CA certificate in base64 encoding) ... -----END CERTIFICATE-----
sequences. Before, between, and after the certificates text is allowed which can be used e.g. for descriptions of the certificates.
The CCAAffiillee is processed on execution of the _S_S_L___C_T_X___l_o_a_d___v_e_r_i_f_y___l_o_c_a_t_i_o_n_s_(_) function.
If CCAAppaatthh is not NULL, it points to a directory containing CA certificates in PEM format. The files each contain one CA certificate. The files are looked up by the CA subject name hash value, which must hence be available. If more than one CA certificate with the same name hash value exist, the extension must be different (e.g. 9d66eef0.0, 9d66eef0.1 etc). The search is performed in the ordering of the extension number, regardless of other properties of the certificates. Use the cc__rreehhaasshh utility to create the necessary links.
The certificates in CCAAppaatthh are only looked up when required, e.g. when building the certificate chain or when actually performing the verification of a peer certificate.
When looking up CA certificates, the OpenSSL library will first search the certificates in CCAAffiillee, then those in CCAAppaatthh. Certificate matching is done based on the subject name, the key identifier (if present), and the serial number as taken from the certificate to be verified. If these data do not match, the next certificate will be tried. If a first certificate matching the parameters is found, the verification process will be performed; no other certificates for the same parameters will be searched in case of failure.
In server mode, when requesting a client certificate, the server must send the list of CAs of which it will accept client certificates. This list is not influenced by the contents of CCAAffiillee or CCAAppaatthh and must explicitly be set using the _S_S_L___C_T_X___s_e_t___c_l_i_e_n_t___C_A___l_i_s_t(3) family of functions.
When building its own certificate chain, an OpenSSL client/server will try to fill in missing certificates from CCAAffiillee/CCAAppaatthh, if the certificate chain was not explicitly specified (see _S_S_L___C_T_X___a_d_d___e_x_t_r_a___c_h_a_i_n___c_e_r_t(3), _S_S_L___C_T_X___u_s_e___c_e_r_t_i_f_i_c_a_t_e(3).
#!/bin/sh rm CAfile.pem for i in ca1.pem ca2.pem ca3.pem ; do openssl x509 -in $i -text >> CAfile.pem done
Prepare the directory /some/where/certs containing several CA certificates for use as CCAAppaatthh:
cd /some/where/certs c_rehash .