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 "X509_STORE_CTX_NEW 3"
way too many mistakes in technical documents.
\fBX509_STORE_CTX_new() returns a newly initialised X509_STORE_CTX structure.
\fBX509_STORE_CTX_cleanup() internally cleans up an X509_STORE_CTX structure. The context can then be reused with a new call to X509_STORE_CTX_init().
\fBX509_STORE_CTX_free() completely frees up ctx. After this call ctx is no longer valid. If ctx is \s-1NULL\s0 nothing is done.
\fBX509_STORE_CTX_init() sets up ctx for a subsequent verification operation. It must be called before each call to X509_verify_cert(), i.e. a ctx is only good for one call to X509_verify_cert(); if you want to verify a second certificate with the same ctx then you must call X509_STORE_CTX_cleanup() and then X509_STORE_CTX_init() again before the second call to \fBX509_verify_cert(). The trusted certificate store is set to store, the end entity certificate to be verified is set to x509 and a set of additional certificates (which will be untrusted but may be used to build the chain) in \fBchain. Any or all of the store, x509 and chain parameters can be \fB\s-1NULL\s0.
\fBX509_STORE_CTX_set0_trusted_stack() sets the set of trusted certificates of \fBctx to sk. This is an alternative way of specifying trusted certificates instead of using an X509_STORE.
\fBX509_STORE_CTX_set_cert() sets the certificate to be verified in ctx to \fBx.
\fBX509_STORE_CTX_set0_verified_chain() sets the validated chain used by ctx to be chain. Ownership of the chain is transferred to ctx and should not be free'd by the caller. \fBX509_STORE_CTX_get0_chain() returns the internal pointer used by the \fBctx that contains the validated chain.
\fBX509_STORE_CTX_set0_crls() sets a set of CRLs to use to aid certificate verification to sk. These CRLs will only be used if \s-1CRL\s0 verification is enabled in the associated X509_VERIFY_PARAM structure. This might be used where additional \*(L"useful\*(R" CRLs are supplied as part of a protocol, for example in a PKCS#7 structure.
\fBX509_STORE_CTX_get0_param() retrieves an internal pointer to the verification parameters associated with ctx.
\fBX509_STORE_CTX_get0_untrusted() retrieves an internal pointer to the stack of untrusted certificates associated with ctx.
\fBX509_STORE_CTX_set0_untrusted() sets the internal point to the stack of untrusted certificates associated with ctx to sk.
\fBX509_STORE_CTX_set0_param() sets the internal verification parameter pointer to param. After this call param should not be used.
\fBX509_STORE_CTX_set_default() looks up and sets the default verification method to name. This uses the function X509_VERIFY_PARAM_lookup() to find an appropriate set of parameters from name.
\fBX509_STORE_CTX_get_num_untrusted() returns the number of untrusted certificates that were used in building the chain following a call to X509_verify_cert().
\fBX509_STORE_CTX_set_verify() provides the capability for overriding the default verify function. This function is responsible for verifying chain signatures and expiration times.
A verify function is defined as an X509_STORE_CTX_verify type which has the following signature:
.Vb 1 int (*verify)(X509_STORE_CTX *); .Ve
This function should receive the current X509_STORE_CTX as a parameter and return 1 on success or 0 on failure.
X509 certificates may contain information about what purposes keys contained within them can be used for. For example \*(L"\s-1TLS WWW\s0 Server Authentication\*(R" or \*(L"Email Protection\*(R". This \*(L"key usage\*(R" information is held internally to the certificate itself. In addition the trust store containing trusted certificates can declare what purposes we trust different certificates for. This \*(L"trust\*(R" information is not held within the certificate itself but is \*(L"meta\*(R" information held alongside it. This \*(L"meta\*(R" information is associated with the certificate after it is issued and could be determined by a system administrator. For example a certificate might declare that it is suitable for use for both \*(L"\s-1TLS WWW\s0 Server Authentication\*(R" and \*(L"\s-1TLS\s0 Client Authentication\*(R", but a system administrator might only trust it for the former. An X.509 certificate extension exists that can record extended key usage information to supplement the purpose information described above. This extended mechanism is arbitrarily extensible and not well suited for a generic library \s-1API\s0; applications that need to validate extended key usage information in certifiates will need to define a custom \*(L"purpose\*(R" (see below) or supply a nondefault verification callback (X509_STORE_set_verify_cb_func\|(3)).
\fBX509_STORE_CTX_set_purpose() sets the purpose for the target certificate being verified in the ctx. Built-in available values for the purpose argument are X509_PURPOSE_SSL_CLIENT, X509_PURPOSE_SSL_SERVER, \fBX509_PURPOSE_NS_SSL_SERVER, X509_PURPOSE_SMIME_SIGN, \fBX509_PURPOSE_SMIME_ENCRYPT, X509_PURPOSE_CRL_SIGN, X509_PURPOSE_ANY, \fBX509_PURPOSE_OCSP_HELPER and X509_PURPOSE_TIMESTAMP_SIGN. It is also possible to create a custom purpose value. Setting a purpose will ensure that the key usage declared within certificates in the chain being verified is consistent with that purpose as well as, potentially, other checks. Every purpose also has an associated default trust value which will also be set at the same time. During verification this trust setting will be verified to check it is consistent with the trust set by the system administrator for certificates in the chain.
\fBX509_STORE_CTX_set_trust() sets the trust value for the target certificate being verified in the ctx. Built-in available values for the trust argument are X509_TRUST_COMPAT, X509_TRUST_SSL_CLIENT, \fBX509_TRUST_SSL_SERVER, X509_TRUST_EMAIL, X509_TRUST_OBJECT_SIGN, \fBX509_TRUST_OCSP_SIGN, X509_TRUST_OCSP_REQUEST and X509_TRUST_TSA. It is also possible to create a custom trust value. Since X509_STORE_CTX_set_purpose() also sets the trust value it is normally sufficient to only call that function. If both are called then X509_STORE_CTX_set_trust() should be called after \fBX509_STORE_CTX_set_purpose() since the trust setting of the last call will be used.
It should not normally be necessary for end user applications to call \fBX509_STORE_CTX_purpose_inherit() directly. Typically applications should call \fBX509_STORE_CTX_set_purpose() or X509_STORE_CTX_set_trust() instead. Using this function it is possible to set the purpose and trust values for the ctx at the same time. The def_purpose and purpose arguments can have the same purpose values as described for X509_STORE_CTX_set_purpose() above. The trust argument can have the same trust values as described in \fBX509_STORE_CTX_set_trust() above. Any of the def_purpose, purpose or \fItrust values may also have the value 0 to indicate that the supplied parameter should be ignored. After calling this function the purpose to be used for verification is set from the purpose argument, and the trust is set from the trust argument. If trust is 0 then the trust value will be set from the default trust value for purpose. If the default trust value for the purpose is X509_TRUST_DEFAULT and trust is 0 then the default trust value associated with the def_purpose value is used for the trust setting instead.
\fBX509_STORE_CTX_init() returns 1 for success or 0 if an error occurred.
\fBX509_STORE_CTX_get0_param() returns a pointer to an X509_VERIFY_PARAM structure or \s-1NULL\s0 if an error occurred.
\fBX509_STORE_CTX_cleanup(), X509_STORE_CTX_free(), \fBX509_STORE_CTX_set0_trusted_stack(), \fBX509_STORE_CTX_set_cert(), \fBX509_STORE_CTX_set0_crls() and X509_STORE_CTX_set0_param() do not return values.
\fBX509_STORE_CTX_set_default() returns 1 for success or 0 if an error occurred.
\fBX509_STORE_CTX_get_num_untrusted() returns the number of untrusted certificates used.
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>.