Standard preamble:
========================================================================
..
.... Set up some character translations and predefined strings. \*(-- will
give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
double quote, and \*(R" will give a right double quote. \*(C+ will
give a nicer C++. Capital omega is used to do unbreakable dashes and
therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
nothing in troff, for use with C<>.
.tr \(*W- . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\}
Escape single quotes in literal strings from groff's Unicode transform.
If the F register is turned on, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.
Avoid warning from groff about undefined register 'F'.
.. .nr rF 0 . if \nF \{ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{ . nr % 0 . nr F 2 . \} . \} .\} .rr rF
Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] .\} . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents . \" corrections for vroff . \" for low resolution devices (crt and lpr) \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} ========================================================================
Title "SSL_CTX_use_certificate 3"
way too many mistakes in technical documents.
The SSL_CTX_* class of functions loads the certificates and keys into the \s-1SSL_CTX\s0 object ctx. The information is passed to \s-1SSL\s0 objects ssl created from ctx with SSL_new\|(3) by copying, so that changes applied to ctx do not propagate to already existing \s-1SSL\s0 objects.
The SSL_* class of functions only loads certificates and keys into a specific \s-1SSL\s0 object. The specific information is kept, when \fISSL_clear\|(3) is called for this \s-1SSL\s0 object.
\fISSL_CTX_use_certificate() loads the certificate x into ctx, \fISSL_use_certificate() loads x into ssl. The rest of the certificates needed to form the complete certificate chain can be specified using the \fISSL_CTX_add_extra_chain_cert\|(3) function.
\fISSL_CTX_use_certificate_ASN1() loads the \s-1ASN1\s0 encoded certificate from the memory location d (with length len) into ctx, \fISSL_use_certificate_ASN1() loads the \s-1ASN1\s0 encoded certificate into ssl.
\fISSL_CTX_use_certificate_file() loads the first certificate stored in file into ctx. The formatting type of the certificate must be specified from the known types \s-1SSL_FILETYPE_PEM, SSL_FILETYPE_ASN1.\s0 \fISSL_use_certificate_file() loads the certificate from file into ssl. See the \s-1NOTES\s0 section on why SSL_CTX_use_certificate_chain_file() should be preferred.
\fISSL_CTX_use_certificate_chain_file() loads a certificate chain from \fBfile into ctx. The certificates must be in \s-1PEM\s0 format and must be sorted starting with the subject's certificate (actual client or server certificate), followed by intermediate \s-1CA\s0 certificates if applicable, and ending at the highest level (root) \s-1CA.\s0 There is no corresponding function working on a single \s-1SSL\s0 object.
\fISSL_CTX_use_PrivateKey() adds pkey as private key to ctx. \fISSL_CTX_use_RSAPrivateKey() adds the private key rsa of type \s-1RSA\s0 to ctx. SSL_use_PrivateKey() adds pkey as private key to ssl; \fISSL_use_RSAPrivateKey() adds rsa as private key of type \s-1RSA\s0 to ssl. If a certificate has already been set and the private does not belong to the certificate an error is returned. To change a certificate, private key pair the new certificate needs to be set with SSL_use_certificate() or SSL_CTX_use_certificate() before setting the private key with \fISSL_CTX_use_PrivateKey() or SSL_use_PrivateKey().
\fISSL_CTX_use_PrivateKey_ASN1() adds the private key of type pk stored at memory location d (length len) to ctx. \fISSL_CTX_use_RSAPrivateKey_ASN1() adds the private key of type \s-1RSA\s0 stored at memory location d (length len) to ctx. \fISSL_use_PrivateKey_ASN1() and SSL_use_RSAPrivateKey_ASN1() add the private key to ssl.
\fISSL_CTX_use_PrivateKey_file() adds the first private key found in \fBfile to ctx. The formatting type of the certificate must be specified from the known types \s-1SSL_FILETYPE_PEM, SSL_FILETYPE_ASN1.\s0 \fISSL_CTX_use_RSAPrivateKey_file() adds the first private \s-1RSA\s0 key found in \fBfile to ctx. SSL_use_PrivateKey_file() adds the first private key found in file to ssl; SSL_use_RSAPrivateKey_file() adds the first private \s-1RSA\s0 key found to ssl.
\fISSL_CTX_check_private_key() checks the consistency of a private key with the corresponding certificate loaded into ctx. If more than one key/certificate pair (\s-1RSA/DSA\s0) is installed, the last item installed will be checked. If e.g. the last item was a \s-1RSA\s0 certificate or key, the \s-1RSA\s0 key/certificate pair will be checked. SSL_check_private_key() performs the same check for ssl. If no key/certificate was explicitly added for this ssl, the last item added into ctx will be checked.
When reading certificates and private keys from file, files of type \s-1SSL_FILETYPE_ASN1 \s0(also known as \s-1DER\s0, binary encoding) can only contain one certificate or private key, consequently \fISSL_CTX_use_certificate_chain_file() is only applicable to \s-1PEM\s0 formatting. Files of type \s-1SSL_FILETYPE_PEM\s0 can contain more than one item.
\fISSL_CTX_use_certificate_chain_file() adds the first certificate found in the file to the certificate store. The other certificates are added to the store of chain certificates using \fISSL_CTX_add_extra_chain_cert\|(3). There exists only one extra chain store, so that the same chain is appended to both types of certificates, \s-1RSA\s0 and \s-1DSA\s0! If it is not intended to use both type of certificate at the same time, it is recommended to use the \fISSL_CTX_use_certificate_chain_file() instead of the \fISSL_CTX_use_certificate_file() function in order to allow the use of complete certificate chains even when no trusted \s-1CA\s0 storage is used or when the \s-1CA\s0 issuing the certificate shall not be added to the trusted \s-1CA\s0 storage.
If additional certificates are needed to complete the chain during the \s-1TLS\s0 negotiation, \s-1CA\s0 certificates are additionally looked up in the locations of trusted \s-1CA\s0 certificates, see \fISSL_CTX_load_verify_locations\|(3).
The private keys loaded from file can be encrypted. In order to successfully load encrypted keys, a function returning the passphrase must have been supplied, see \fISSL_CTX_set_default_passwd_cb\|(3). (Certificate files might be encrypted as well from the technical point of view, it however does not make sense as the data in the certificate is considered public anyway.)