Automatically generated by Pod::Man 4.14 (Pod::Simple 3.42)

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 >0, 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_CHECK_CHAIN 3" For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
SSL_check_chain - check certificate chain suitability Header "SYNOPSIS" .Vb 1 #include <openssl/ssl.h> \& int SSL_check_chain(SSL *s, X509 *x, EVP_PKEY *pk, STACK_OF(X509) *chain); .Ve Header "DESCRIPTION" \fBSSL_check_chain() checks whether certificate x, private key pk and certificate chain chain is suitable for use with the current session \fBs. Header "RETURN VALUES" \fBSSL_check_chain() returns a bitmap of flags indicating the validity of the chain.

\fB\s-1CERT_PKEY_VALID\s0: the chain can be used with the current session. If this flag is not set then the certificate will never be used even if the application tries to set it because it is inconsistent with the peer preferences.

\fB\s-1CERT_PKEY_SIGN\s0: the \s-1EE\s0 key can be used for signing.

\fB\s-1CERT_PKEY_EE_SIGNATURE\s0: the signature algorithm of the \s-1EE\s0 certificate is acceptable.

\fB\s-1CERT_PKEY_CA_SIGNATURE\s0: the signature algorithms of all \s-1CA\s0 certificates are acceptable.

\fB\s-1CERT_PKEY_EE_PARAM\s0: the parameters of the end entity certificate are acceptable (e.g. it is a supported curve).

\fB\s-1CERT_PKEY_CA_PARAM\s0: the parameters of all \s-1CA\s0 certificates are acceptable.

\fB\s-1CERT_PKEY_EXPLICIT_SIGN\s0: the end entity certificate algorithm can be used explicitly for signing (i.e. it is mentioned in the signature algorithms extension).

\fB\s-1CERT_PKEY_ISSUER_NAME\s0: the issuer name is acceptable. This is only meaningful for client authentication.

\fB\s-1CERT_PKEY_CERT_TYPE\s0: the certificate type is acceptable. Only meaningful for client authentication.

\fB\s-1CERT_PKEY_SUITEB\s0: chain is suitable for Suite B use.

Header "NOTES" \fBSSL_check_chain() must be called in servers after a client hello message or in clients after a certificate request message. It will typically be called in the certificate callback.

An application wishing to support multiple certificate chains may call this function on each chain in turn: starting with the one it considers the most secure. It could then use the chain of the first set which returns suitable flags.

As a minimum the flag \s-1CERT_PKEY_VALID\s0 must be set for a chain to be usable. An application supporting multiple chains with different \s-1CA\s0 signature algorithms may also wish to check \s-1CERT_PKEY_CA_SIGNATURE\s0 too. If no chain is suitable a server should fall back to the most secure chain which sets \s-1CERT_PKEY_VALID\s0.

The validity of a chain is determined by checking if it matches a supported signature algorithm, supported curves and in the case of client authentication certificate types and issuer names.

Since the supported signature algorithms extension is only used in \s-1TLS 1.2, TLS 1.3\s0 and \s-1DTLS 1.2\s0 the results for earlier versions of \s-1TLS\s0 and \s-1DTLS\s0 may not be very useful. Applications may wish to specify a different \*(L"legacy\*(R" chain for earlier versions of \s-1TLS\s0 or \s-1DTLS.\s0

Header "SEE ALSO" \fBSSL_CTX_set_cert_cb\|(3), \fBssl\|(7) Header "COPYRIGHT" Copyright 2015-2018 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the OpenSSL license (the \*(L"License\*(R"). You may not use this file except in compliance with the License. You can obtain a copy in the file \s-1LICENSE\s0 in the source distribution or at <https://www.openssl.org/source/license.html>.