"Fossies" - the Fresh Open Source Software Archive

Member "openssl-1.0.2q/doc/ssl/SSL_check_chain.pod" (20 Nov 2018, 2860 Bytes) of package /linux/misc/openssl-1.0.2q.tar.gz:

Caution: As a special service "Fossies" has tried to format the requested pod source page into HTML format but links to other pod pages may be missing or even errorneous. Alternatively you can here view or download the uninterpreted pod source code. A member file download can also be achieved by clicking within a package contents listing on the according byte size field. See also the last Fossies "Diffs" side-by-side code changes report for "SSL_check_chain.pod": 1.1.0g_vs_1.1.1-pre2.


SSL_check_chain - check certificate chain suitability


 #include <openssl/ssl.h>

 int SSL_check_chain(SSL *s, X509 *x, EVP_PKEY *pk, STACK_OF(X509) *chain);


SSL_check_chain() checks whether certificate x, private key pk and certificate chain chain is suitable for use with the current session s.


SSL_check_chain() returns a bitmap of flags indicating the validity of the chain.

CERT_PKEY_VALID: 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.

CERT_PKEY_SIGN: the EE key can be used for signing.

CERT_PKEY_EE_SIGNATURE: the signature algorithm of the EE certificate is acceptable.

CERT_PKEY_CA_SIGNATURE: the signature algorithms of all CA certificates are acceptable.

CERT_PKEY_EE_PARAM: the parameters of the end entity certificate are acceptable (e.g. it is a supported curve).

CERT_PKEY_CA_PARAM: the parameters of all CA certificates are acceptable.

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

CERT_PKEY_ISSUER_NAME: the issuer name is acceptable. This is only meaningful for client authentication.

CERT_PKEY_CERT_TYPE: the certificate type is acceptable. Only meaningful for client authentication.

CERT_PKEY_SUITEB: chain is suitable for Suite B use.


SSL_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 CERT_PKEY_VALID must be set for a chain to be usable. An application supporting multiple chains with different CA signature algorithms may also wish to check CERT_PKEY_CA_SIGNATURE too. If no chain is suitable a server should fall back to the most secure chain which sets CERT_PKEY_VALID.

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 TLS 1.2 and DTLS 1.2 the results for earlier versions of TLS and DTLS may not be very useful. Applications may wish to specify a different "legacy" chain for earlier versions of TLS or DTLS.


SSL_CTX_set_cert_cb(3), ssl(3)