SSL_check_chain (3)

Leading comments

Automatically generated by Pod::Man 4.07 (Pod::Simple 3.32)

Standard preamble:
========================================================================

(The comments found at the beginning of the groff file "man3/SSL_check_chain.3ssl".)

NAME

SSL_check_chain - check certificate chain suitability

SYNOPSIS

 #include <openssl/ssl.h>

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

DESCRIPTION

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

RETURN VALUES

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

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

: the key can be used for signing.

: the signature algorithm of the certificate is acceptable.

: the signature algorithms of all certificates are acceptable.

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

: the parameters of all certificates are acceptable.

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

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

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

: chain is suitable for Suite B use.

NOTES

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

must be set for a chain to be usable. An application supporting multiple chains with different signature algorithms may also wish to check too. If no chain is suitable a server should fall back to the most secure chain which sets .

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

and the results for earlier versions of and may not be very useful. Applications may wish to specify a different ``legacy'' chain for earlier versions of or

SEE ALSO

SSL_CTX_set_cert_cb(3), ssl(3)