Usable X.509 errors: OpenSSL
Our goal is to simplify the ecosystem by consolidating the errors and their documentation (similarly to web documentation) and better explaining what the validation errors mean.
Correctly validating X.509 certificates turns out to be pretty complicated (e.g., Georgiev2012, Ukrop2019). Yet certificate validation is crucial for secure communication on the Internet (think TLS).
For every error, we aim to provide our redesigned documentation ( ), an example certificate ( ), original documentation provided by the library ( , unused or deprecated errors denoted by ). Furthermore, we provide links to corresponding errors from other libraries ( ). In the future, we plan on adding error frequencies based on IP-wide scans and elaborating on the consequences of individual errors.
Time validity errors
Errors occuring when a certificate is outside its validity period or when it is revoked by its CA.
Relevant links: Certificate Validity (RFC 5280), Certificate Revocation (RFC 5280)
Original documentation:
The certificate is not yet valid: the notBefore date is after the current time. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Corresponding errors:
- GnuTLS/GNUTLS_CERT_NOT_ACTIVATED
- Botan/CERT_NOT_YET_VALID
- mbedTLS/MBEDTLS_X509_BADCERT_FUTURE
Redesigned documentation:
The certificate has expired (its validity period passed).
Explanation
Every certificate is issued for a specific time period (determined by notBefore and notAfter fields in the certificate). The current time seems to be past the notAfter value. Therefore, the certificate is no longer valid.
Security perspective
The certificate is not valid anymore. That means the issuing Certificate Authority (CA) does guarantee the information in it is still correct. Moreover, expired certificates are removed from Certificate Revocation Lists (CRLs). That means the certificate might have been revoked in the past (e.g., because of a leaked private key), but we cannot check anymore. Thus, the server presenting this certificate may not be who it claims.
Next steps
First, ensure that the date, time and time zone are set correctly on your device to eliminate the possibility of local misconfiguration. If the time settings are correct, you should get a new valid certificate from the CA.
Original documentation:
The certificate has expired: that is the notAfter date is before the current time. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Corresponding errors:
- GnuTLS/GNUTLS_CERT_EXPIRED
- Botan/CERT_HAS_EXPIRED
- mbedTLS/MBEDTLS_X509_BADCERT_EXPIRED
Original documentation:
The CRL is not yet valid. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -CRLfile ca.crl -crl_check endpoint.crt
Corresponding errors:
Original documentation:
The CRL has expired. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -CRLfile ca.crl -crl_check endpoint.crt
Corresponding errors:
Original documentation:
The certificate has been revoked. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -CRLfile ca.crl -crl_check endpoint.crt
Corresponding errors:
- GnuTLS/GNUTLS_CERT_REVOKED
- Botan/CERT_IS_REVOKED
- mbedTLS/MBEDTLS_X509_BADCERT_REVOKED
Trust or chain related errors
These errors occur when the trust chain to the root certificate is not built correctly or fails.
Relevant links: Certificate Paths (RFC 5280), Certificate Revocation Lists (RFC 5280), OCSP (RFC 2560)
Original documentation:
The issuer certificate of a looked up certificate could not be found. This normally means the list of trusted certificates is not complete. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile subca.crt -untrusted subca.crt endpoint.crt
Original documentation:
The issuer certificate could not be found: this occurs if the issuer certificate of an untrusted certificate cannot be found. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify endpoint.crt
Corresponding errors:
- Botan/CERT_ISSUER_NOT_FOUND
- GnuTLS/GNUTLS_CERT_SIGNER_NOT_FOUND
- mbedTLS/MBEDTLS_X509_BADCERT_NOT_TRUSTED
Redesigned documentation:
The provided certificate is self-signed and it is not present in the list of trusted certificates.
Explanation
The provided certificate is self-signed (the issuer and subject fields are the same). Self-signed certificates usually serve as the root of trust in certificate chains belonging to the Certificate Authorities (CA). However, this certificate is at “zero depth,” i.e., it does not form a certificate chain. Neither is it present in the list of explicitly trusted CAs in your system.
Security perspective
Anyone can issue a self-signed certificate. Thus, the information contained in the certificate is not reliable. Therefore, the server presenting this certificate may not be who it claims.
Next steps
Try to find out if the self-signed certificate was expected at this place. Try to get a proper CA-signed certificated as self-signed certificates are not recommended even for testing purposes. If you are absolutely certain this is the certificate issued by a trustworthy party, you can mark it as trusted by your system. The provided certificate is self-signed and it cannot be found in the list of trusted certificates.
Original documentation:
The passed certificate is self-signed and the same certificate cannot be found in the list of trusted certificates. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify endpoint.crt
Corresponding errors:
- GnuTLS/GNUTLS_CERT_SIGNER_NOT_FOUND
- Botan/CANNOT_ESTABLISH_TRUST
- mbedTLS/MBEDTLS_X509_BADCERT_NOT_TRUSTED
Original documentation:
The certificate chain could be built up using the untrusted certificates but the root could not be found locally. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -untrusted ca.crt endpoint.crt
Corresponding errors:
- GnuTLS/GNUTLS_CERT_SIGNER_NOT_FOUND
- Botan/CANNOT_ESTABLISH_TRUST
- mbedTLS/MBEDTLS_X509_BADCERT_NOT_TRUSTED
Original documentation:
The certificate chain length is greater than the supplied maximum depth. Unused. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile subca.crt -untrusted subca.crt -verify_depth 0 endpoint.crt
Original documentation:
The CRL of a certificate could not be found. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -crl_check -CAfile ca.crt endpoint.crt
Original documentation:
Unable to get CRL issuer certificate. (source)
Original documentation:
CRL path validation error. (source)
Original documentation:
Different CRL scope. (source)
Original documentation:
No signatures could be verified because the chain contains only one certificate and it is not self signed. (source)
Original documentation:
Path loop. (source)
Unused: Is actively used in the code once in function check_issued in file x509_vfy.c, but cannot be returned outside of that function.
Original documentation:
Returned by the verify callback to indicate that the certificate is not recognized by the OCSP responder. (source)
Original documentation:
Not used as of OpenSSL 1.1.0 as a result of the deprecation of the -issuer_checks option. (source)
Unused: The documentation states that the error code is not used.
Original documentation:
Not used as of OpenSSL 1.1.0 as a result of the deprecation of the -issuer_checks option. (source)
Unused: The documentation states that the error code is not used.
Original documentation:
Not used as of OpenSSL 1.1.0 as a result of the deprecation of the -issuer_checks option. (source)
Unused: The documentation states that the error code is not used.
Original documentation:
Returned by the verify callback to indicate OCSP verification failed. (source)
Basic extension errors
Errors related to extensions in general or to the BasicConstraints standard extension.
Relevant links: Certificate Extensions (RFC 5280), BasicConstraints Extension (RFC 5280)
Original documentation:
Unsupported extension feature. (source)
Unused: As of now only defined in the code but not used.
Original documentation:
A CA certificate is invalid. Either it is not a CA or its extensions are not consistent with the supplied purpose. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -untrusted subca.crt endpoint.crt
Corresponding errors:
- GnuTLS/GNUTLS_CERT_SIGNER_NOT_CA
- Botan/CA_CERT_NOT_FOR_CERT_ISSUER
- mbedTLS/MBEDTLS_X509_BADCERT_NOT_TRUSTED
Redesigned documentation:
The allowed length of the certification path was exceeded.
Explanation
Certification Authorities (CAs) can mandate the maximal length of the trusted certificate chains below their certificate. This is done using the pathLenConstraint field in the basicConstraints extension. If the certificate chain created during validation is longer than this limit, the validation fails due to the violated path length constraint. This limit includes only intermediate certificates – the first (CA) and the last (endpoint) certificates are excluded.
Security perspective
An exceeded certificate path length signifies that one of the sub-authorities issued a certificate it was not allowed. Therefore, the CA or one of the sub-authorities may not be trustworthy.
Next steps
Inspect the certificate chain to find the pathLenConstraint in the basicConstraints extension that was violated. Inform the (sub-)authority issuing this certificate about the violation lower in the certificate chain.
Original documentation:
The basicConstraints pathlength parameter has been exceeded. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -untrusted subca1.crt -untrusted subca2.crt endpoint.crt
Corresponding errors:
- Botan/CERT_CHAIN_TOO_LONG
- GnuTLS/GNUTLS_CERT_SIGNER_CONSTRAINTS_FAILURE
- mbedTLS/MBEDTLS_X509_BADCERT_NOT_TRUSTED
Redesigned documentation:
A critical extension was not recognized or could not be processed.
Explanation
Certificate extensions can be used for extending certificates with additional information. Each extension is either marked as critical or non-critical (in the critical field in the extension). If an extension is marked as critical, it must be processed. If the processing system cannot recognize or process a critical extension, it must reject the certificate.
Security perspective
Marking an extension as critical is a way for the certificate issuer to denote it is absolutely essential to process and understand it. If it is not processed, we may lack the necessary information and misuse the certificate. We may, for example, miss the intended purpose or key usage constraint. Inappropriateong usage circumvents the guarantees of the certificate authority, possibly putting our systems at risk.
Next steps
Inspect the certificate extensions marked with critical: true to find the offender. Make sure that only the necessary extensions are marked as critical. Marking non-standard extensions as critical may cause problems in the general context.
Original documentation:
Unhandled critical extension. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Corresponding errors:
Original documentation:
Unhandled critical CRL extension. (source)
Original documentation:
Invalid or inconsistent certificate extension. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Name related errors
Errors signalizing problems with either hostname verification, NameConstaints standard extension or IP Address Delegation extension.
Relevant links: NameConstaints extension (RFC 5280), IP Address Delegation extension (RFC 3779), Certificate Common Name (RFC 5280)
Redesigned documentation:
The requested hostname does not match the subject name in the certificate.
Explanation
Information about the certificate’s subject (an entity associated with the certificate’s public key) is held in the subjectAltName extension or the subject field. However, the hostname of the server you are connecting to does not match the subject information in the certificate.
Security perspective
You cannot verify the identity of the server to which you are connecting – you should not proceed. The server is either providing a wrong certificate (by being misconfigured) or is deliberately pretending to be a different entity to fool you. Sending or receiving data from unknown servers may put your systems at risk.
Next steps
Compare the server hostname with the subjectAltName extension and the subject field of the certificate. Common misconfigurations include not including server aliases in the certificate (e.g., www.example.com for the server example.com).
Original documentation:
Hostname mismatch. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -verify_hostname www.crocs.muni.cz endpoint.crt
Corresponding errors:
- Botan/CERT_NAME_NOMATCH
- mbedTLS/MBEDTLS_X509_BADCERT_CN_MISMATCH
Original documentation:
Email address mismatch. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -verify_email crocs@muni.cz endpoint.crt
Original documentation:
IP address mismatch. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -verify_ip 192.168.0.0. endpoint.crt
Original documentation:
Permitted subtree violation. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Corresponding errors:
- Botan/NAME_CONSTRAINT_ERROR
- GnuTLS/GNUTLS_CERT_SIGNER_CONSTRAINTS_FAILURE
- mbedTLS/MBEDTLS_X509_BADCERT_NOT_TRUSTED
Original documentation:
Excluded subtree violation. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Corresponding errors:
Original documentation:
Name constraints minimum and maximum not supported. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Original documentation:
Unsupported name constraint type. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Original documentation:
Unsupported or invalid name constraint syntax. (source)
Unused: As of now only defined in the code but not used.
Original documentation:
Unsupported or invalid name syntax. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Original documentation:
RFC 3779 resource not subset of parent's resources. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Usage and policy errors
Errors related to standard extensions CertificatePolicies, KeyUsage and ExtendedKeyUsage.
Relevant links: KeyUsage extension (RFC5280), ExtendedKeyUsage extension (RFC5280), CertificatePolicies extension (RFC5280)
Redesigned documentation:
The certificate’s key is being used for a different purpose than allowed.
Explanation
Certificates can be used for various purposes. It might be desirable to use a certificate only for specific purposes. This is achieved by the keyUsage extension, which defines nine possible usages of the certificate (e.g., digitalSignature or dataEncipherment). End entity certificates can also specify the extended key uses (in the extKeyUsage extension).
Security perspective
Using the certificate for the purpose forbidden in the certificate may pose a risk to your data or systems. (For example, the key’s security may not be sufficient for the forbidden use).
Next steps
Check both the keyUsage and extKeyUsage to see if the listed purposes include the one for which you are attempting to use the certificate.
Original documentation:
The supplied certificate cannot be used for the specified purpose. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -purpose sslserver endpoint.crt
Corresponding errors:
- GnuTLS/GNUTLS_CERT_PURPOSE_MISMATCH
Original documentation:
The root CA is marked to reject the specified purpose. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -purpose sslserver -CAfile sca.crt endpoint.crt
Original documentation:
Invalid or inconsistent certificate policy extension. (source)
Original documentation:
No explicit policy. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -policy_check -explicit_policy -policy 1.3.6.1.4.1.5484.1.10.99.1.0 endpoint.crt
Original documentation:
Key usage does not include CRL signing. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -crl_check -CRLfile ca.crl endpoint.crt
Original documentation:
Key usage does not include digital signature. (source)
Original documentation:
Not used as of OpenSSL 1.1.0 as a result of the deprecation of the -issuer_checks option. (source)
Unused: The documentation states that the error code is not used.
Algorithm related errors
Various errors signalizing usage of invalid or deprecated algorithms.
Relevant links: Algorithm and Key Size Profile for PKI (RFC 7935), Suite B Profile for TLS (RFC 6460)
Original documentation:
EE certificate key too weak. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -auth_level 1 endpoint.crt
Corresponding errors:
- mbedTLS/MBEDTLS_X509_BADCERT_BAD_KEY
Original documentation:
CA certificate key too weak. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -auth_level 1 endpoint.crt
Corresponding errors:
- Botan/SIGNATURE_METHOD_TOO_WEAK
- mbedTLS/MBEDTLS_X509_BADCERT_BAD_KEY
Original documentation:
CA signature digest algorithm too weak. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -auth_level 3 endpoint.crt
Corresponding errors:
- Botan/UNTRUSTED_HASH
- mbedTLS/MBEDTLS_X509_BADCERT_BAD_MD
Original documentation:
Suite B: certificate version invalid. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -suiteB_128_only endpoint.crt
Original documentation:
Suite B: invalid public key algorithm. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -suiteB_192 endpoint.crt
Original documentation:
Suite B: invalid ECC curve. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -suiteB_128_only endpoint.crt
Original documentation:
Suite B: invalid signature algorithm. (source)
Original documentation:
Suite B: curve not allowed for this LOS. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -suiteB_192 endpoint.crt
Original documentation:
Suite B: cannot sign P-384 with P-256. (source)
Formatting errors
These errors occur when a field of the certificate/CRL contains invalid values or is badly formatted.
Relevant links: Certificate Signature (RFC 5280), Certificate Time formatting (RFC 5280), Certificate Signature Algorithm (RFC 5280)
Original documentation:
The signature of the certificate is invalid. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Corresponding errors:
- Botan/SIGNATURE_ERROR
- GnuTLS/GNUTLS_CERT_SIGNATURE_FAILURE
- mbedTLS/MBEDTLS_X509_BADCERT_NOT_TRUSTED
Original documentation:
The signature of the certificate is invalid. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt -CRLfile ca.crl -crl_check endpoint.crt
Corresponding errors:
Original documentation:
The certificate notBefore field contains an invalid time. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Original documentation:
The certificate notAfter field contains an invalid time. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Original documentation:
The CRL lastUpdate field contains an invalid time. (source)
Original documentation:
The CRL nextUpdate field contains an invalid time. (source)
Original documentation:
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. (source)
Original documentation:
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. (source)
Unused: As of now only defined in the code but not used. Also marked as unused in the docs.
Original documentation:
The public key in the certificate SubjectPublicKeyInfo could not be read. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Original documentation:
Issuer certificate doesn't have a public key. (source)
Original documentation:
Subject signature algorithm and issuer public key algorithm mismatch (source)
Uncategorized errors
These errors are not yet categorized, deprecated or not used at all.
Original documentation:
Proxy certificates not allowed, please use -allow_proxy_certs. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Original documentation:
Invalid non-CA certificate has CA markings. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -allow_proxy_certs -CAfile ca.crt endpoint.crt
Original documentation:
Proxy path length constraint exceeded. (source)
Original documentation:
Proxy certificate name violation. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -allow_proxy_certs -CAfile ca.crt -untrusted endpoint.crt proxy.crt
Original documentation:
Invalid certificate verification context. (source)
Original documentation:
Issuer certificate lookup error. (source)
Original documentation:
An error occurred trying to allocate memory. This should never happen. (source)
Original documentation:
Application verification failure. Unused. (source)
Original documentation:
DANE TLSA authentication is enabled, but no TLSA records matched the certificate chain. This error is only possible in s_client(1). (source)
Original documentation:
Certificate Transparency required, but no valid SCTs found. (source)
Original documentation:
Returned by the verify callback to indicate an OCSP verification is needed. (source)
Original documentation:
Unspecified error; should not happen. (source)
Original documentation:
Proxy certificate subject is invalid. It MUST be the same as the issuer with a single CN component added. (source)
Unused: This code is not even defined in the code. It was in OpenSSL 1.1.1 docs, but in current master docs isn't.
Original documentation:
The operation was successful. (source)
Example certificate
Download the certificate archive and validate the contents using a command indicated below. If you are interested in generating such certificate yourself, see the generating script for this case on the project GitHub.
Validate with: openssl verify -CAfile ca.crt endpoint.crt
Corresponding errors:
- Botan/VERIFIED
About the project
The project is developed at the Centre for Research on Cryptography and Security (CRoCS) at Masaryk University, Brno, Czech Republic by Martin Ukrop, Pavol Žáčik, Eric Valčík with the help of Michaela Balážová and Matěj Grabovský. For more details, see the ReadMe file in the project repository on GitHub.
The authors are grateful for the financial support by and Red Hat Czech and Kiwi.com.