X509_STORE_CTX_get_error, X509_STORE_CTX_set_error, X509_STORE_CTX_get_error_depth, X509_STORE_CTX_set_error_depth, X509_STORE_CTX_get_current_cert, X509_STORE_CTX_set_current_cert, X509_STORE_CTX_get0_cert, X509_STORE_CTX_get1_chain, X509_verify_cert_error_string - get or set certificate verification status information
#include <openssl/x509.h>
int X509_STORE_CTX_get_error(const X509_STORE_CTX *ctx);
void X509_STORE_CTX_set_error(X509_STORE_CTX *ctx, int s);
int X509_STORE_CTX_get_error_depth(const X509_STORE_CTX *ctx);
void X509_STORE_CTX_set_error_depth(X509_STORE_CTX *ctx, int depth);
X509 *X509_STORE_CTX_get_current_cert(const X509_STORE_CTX *ctx);
void X509_STORE_CTX_set_current_cert(X509_STORE_CTX *ctx, X509 *x);
X509 *X509_STORE_CTX_get0_cert(const X509_STORE_CTX *ctx);
STACK_OF(X509) *X509_STORE_CTX_get1_chain(const X509_STORE_CTX *ctx);
const char *X509_verify_cert_error_string(long n);These functions are typically called after certificate or chain verification using X509_verify_cert(3) or X509_STORE_CTX_verify(3) has indicated an error or in a verification callback to determine the nature of an error.
X509_STORE_CTX_get_error() returns the error code of ctx. See the "ERROR CODES" section for a full description of all error codes. It may return a code != X509_V_OK even if X509_verify_cert() did not indicate an error, likely because a verification callback function has waived the error.
X509_STORE_CTX_set_error() sets the error code of ctx to s. For example it might be used in a verification callback to set an error based on additional checks.
X509_STORE_CTX_get_error_depth() returns the depth of the error. This is a nonnegative integer representing where in the certificate chain the error occurred. If it is zero it occurred in the end entity certificate, one if it is the certificate which signed the end entity certificate and so on.
X509_STORE_CTX_set_error_depth() sets the error depth. This can be used in combination with X509_STORE_CTX_set_error() to set the depth at which an error condition was detected.
X509_STORE_CTX_get_current_cert() returns the current certificate in ctx. If an error occurred, the current certificate will be the one that is most closely related to the error, or possibly NULL if no such certificate is relevant.
X509_STORE_CTX_set_current_cert() sets the certificate x in ctx which caused the error. This value is not intended to remain valid for very long, and remains owned by the caller. It may be examined by a verification callback invoked to handle each error encountered during chain verification and is no longer required after such a callback. If a callback wishes the save the certificate for use after it returns, it needs to increment its reference count via X509_up_ref(3). Once such a saved certificate is no longer needed it can be freed with X509_free(3).
X509_STORE_CTX_get0_cert() retrieves an internal pointer to the certificate being verified by the ctx. It may be NULL if a raw public key is being verified.
X509_STORE_CTX_get1_chain() returns a complete validate chain if a previous verification is successful. Otherwise the returned chain may be incomplete or invalid. The returned chain persists after the ctx structure is freed. When it is no longer needed it should be free up using:
OSSL_STACK_OF_X509_free(chain);X509_verify_cert_error_string() returns a human readable error string for verification error n.
X509_STORE_CTX_get_error() returns X509_V_OK or an error code.
X509_STORE_CTX_get_error_depth() returns a nonnegative error depth.
X509_STORE_CTX_get_current_cert() returns the certificate which caused the error or NULL if no certificate is relevant to the error.
X509_verify_cert_error_string() returns a human readable error string for verification error n.
A list of error codes and messages is shown below. Some of the error codes are defined but currently never returned: these are described as "unused".
The operation was successful.
Unspecified error; should not happen.
The issuer certificate of a locally looked up certificate could not be found. This normally means the list of trusted certificates is not complete. To allow any certificate (not only a self-signed one) in the trust store to terminate the chain the X509_V_FLAG_PARTIAL_CHAIN flag may be set.
The CRL of a certificate could not be found.
The certificate signature could not be decrypted. This means that the actual signature value could not be determined rather than it not matching the expected value, this is only meaningful for RSA keys.
The CRL signature could not be decrypted: this means that the actual signature value could not be determined rather than it not matching the expected value. Unused.
The public key in the certificate SubjectPublicKeyInfo field could not be read.
The signature of the certificate is invalid.
The signature of the CRL is invalid.
The certificate is not yet valid: the notBefore date is after the current time.
The certificate has expired: that is the notAfter date is before the current time.
The CRL is not yet valid.
The CRL has expired.
The certificate notBefore field contains an invalid time.
The certificate notAfter field contains an invalid time.
The CRL lastUpdate field contains an invalid time.
The CRL nextUpdate field contains an invalid time.
An error occurred trying to allocate memory.
The passed certificate is self-signed and the same certificate cannot be found in the list of trusted certificates.
The certificate chain could be built up using the untrusted certificates but no suitable trust anchor (which typically is a self-signed root certificate) could be found in the trust store.
The issuer certificate could not be found: this occurs if the issuer certificate of an untrusted certificate cannot be found.
No signatures could be verified because the chain contains only one certificate and it is not self-signed and the X509_V_FLAG_PARTIAL_CHAIN flag is not set.
The certificate chain length is greater than the supplied maximum depth.
The certificate has been revoked.
The issuer certificate does not have a public key.
The basicConstraints path-length parameter has been exceeded.
The target certificate cannot be used for the specified purpose.
The root CA is not marked as trusted for the specified purpose.
The root CA is marked to reject the specified purpose.
The current candidate issuer certificate was rejected because its subject name did not match the issuer name of the current certificate.
The current candidate issuer certificate was rejected because its subject key identifier was present and did not match the authority key identifier current certificate.
The current candidate issuer certificate was rejected because its issuer name and serial number was present and did not match the authority key identifier of the current certificate.
The current candidate issuer certificate was rejected because its keyUsage extension does not permit certificate signing.
Unable to get CRL issuer certificate.
Unhandled critical extension.
Key usage does not include CRL signing.
Unhandled critical CRL extension.
Invalid non-CA certificate has CA markings.
Proxy path length constraint exceeded.
Key usage does not include digital signature, and therefore cannot sign certificates.
Proxy certificates not allowed unless the X509_V_FLAG_ALLOW_PROXY_CERTS flag is set.
A certificate extension had an invalid value (for example an incorrect encoding) or some value inconsistent with other extensions.
A certificate policies extension had an invalid value (for example an incorrect encoding) or some value inconsistent with other extensions. This error only occurs if policy processing is enabled.
The verification flags were set to require and explicit policy but none was present.
The only CRLs that could be found did not match the scope of the certificate.
Some feature of a certificate extension is not supported. Unused.
See RFC 3779 for details.
A name constraint violation occurred in the permitted subtrees.
A name constraint violation occurred in the excluded subtrees.
A certificate name constraints extension included a minimum or maximum field: this is not supported.
An application specific error. This will never be returned unless explicitly set by an application callback.
An unsupported name constraint type was encountered. OpenSSL currently only supports directory name, DNS name, email and URI types.
The format of the name constraint is not recognised: for example an email address format of a form not mentioned in RFC3280. This could be caused by a garbage extension or some new feature not currently supported.
Unsupported or invalid name syntax.
An error occurred when attempting to verify the CRL path. This error can only happen if extended CRL checking is enabled.
Path loop.
Hostname mismatch.
Email address mismatch.
IP address mismatch.
DANE TLSA authentication is enabled, but no TLSA records matched the certificate chain. This error is only possible in openssl-s_client(1).
EE certificate key too weak.
CA certificate key too weak.
CA signature digest algorithm too weak.
Invalid certificate verification context.
Issuer certificate lookup error.
Certificate Transparency required, but no valid SCTs found.
Proxy subject name violation.
Returned by the verify callback to indicate an OCSP verification is needed.
Returned by the verify callback to indicate OCSP verification failed.
Returned by the verify callback to indicate that the certificate is not recognized by the OCSP responder.
Cannot find certificate signature algorithm.
The issuer's public key is not of the type required by the signature in the subject's certificate.
The algorithm given in the certificate info is inconsistent with the one used for the certificate signature.
A CA certificate is invalid. Either it is not a CA or its extensions are not consistent with the supplied purpose.
No TLS records were configured to validate the raw public key, or DANE was not enabled on the connection.
The above functions should be used instead of directly referencing the fields in the X509_VERIFY_CTX structure.
In versions of OpenSSL before 1.0 the current certificate returned by X509_STORE_CTX_get_current_cert() was never NULL. Applications should check the return value before printing out any debugging information relating to the current certificate.
If an unrecognised error code is passed to X509_verify_cert_error_string() the numerical value of the unknown code is returned in a static buffer. This is not thread safe but will never happen unless an invalid code is passed.
Previous versions of this documentation swapped the meaning of the X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT and X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY error codes.
X509_verify_cert(3), X509_STORE_CTX_verify(3), X509_up_ref(3), X509_free(3).
Copyright 2009-2023 The OpenSSL Project Authors. All Rights Reserved.
Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at https://www.openssl.org/source/license.html.