X509_store_add_cert

 admin

Name

Class OpenSSL::X509::Store The X509 certificate store holds trusted CA certificates used to verify peer certificates. The easiest way to create a useful certificate store is: certstore = OpenSSL:: X509:: Store. This will use your system's built-in certificates. Add certification authority for performing verification. Void addcertificateauthority (const constbuffer & ca). This function is used to add one trusted certification authority from a memory buffer. X509STORE 与 X509STORECTX的用法区别.

SSL_CTX_set_verify, SSL_set_verify, SSL_CTX_set_verify_depth, SSL_set_verify_depth - set peer certificate verification parameters

Synopsis

Description

SSL_CTX_set_verify() sets the verification flags for ctx to be mode and specifies the verify_callback function to be used. If nocallback function shall be specified, the NULL pointer can be used for verify_callback.

SSL_set_verify() sets the verification flags for ssl to be mode and specifies the verify_callback function to be used. If nocallback function shall be specified, the NULL pointer can be used for verify_callback. In this case last verify_callback setspecifically for this ssl remains. If no special callback was set before, the default callback for the underlying ctx is used, that wasvalid at the time ssl was created with ssl_new(3).

SSL_CTX_set_verify_depth() sets the maximum depth for the certificate chain verification that shall be allowed for ctx. (See theBUGS section.)

SSL_set_verify_depth() sets the maximum depth for the certificate chain verification that shall be allowed for ssl. (See theBUGS section.)

Notes

The verification of certificates can be controlled by a set of logically or'ed mode flags:

SSL_VERIFY_NONE
Server mode: the server will not send a client certificate request to the client, so the client will not send a certificate.

Client mode: if not using an anonymous cipher (by default disabled), the server will send a certificate which will be checked. The result of thecertificate verification process can be checked after the TLS/SSL handshake using the ssl_get_verify_result(3) function. The handshakewill be continued regardless of the verification result.

SSL_VERIFY_PEER
Server mode: the server sends a client certificate request to the client. The certificate returned (if any) is checked. If the verification processfails, the TLS/SSL handshake is immediately terminated with an alert message containing the reason for the verification failure. The behaviourcan be controlled by the additional SSL_VERIFY_FAIL_IF_NO_PEER_CERT and SSL_VERIFY_CLIENT_ONCE flags.

Client mode: the server certificate is verified. If the verification process fails, the TLS/SSL handshake is immediately terminatedwith an alert message containing the reason for the verification failure. If no server certificate is sent, because an anonymous cipher is used,SSL_VERIFY_PEER is ignored.

SSL_VERIFY_FAIL_IF_NO_PEER_CERT
Server mode: if the client did not return a certificate, the TLS/SSL handshake is immediately terminated with a 'handshake failure'alert. This flag must be used together with SSL_VERIFY_PEERX509_store_add_cert crash .

Client mode: ignored

SSL_VERIFY_CLIENT_ONCE

X509_store_add_cert Example

Server mode: only request a client certificate on the initial TLS/SSL handshake. Do not ask for a client certificate again in case ofa renegotiation. This flag must be used together with SSL_VERIFY_PEER .

Client mode: ignored

Exactly one of the X509_store_add_certmode flags SSL_VERIFY_NONE and SSL_VERIFY_PEER must be set at any time.

The actual verification procedure is performed either using the built-in verification procedure or using another application provided verification functionset with ssl_ctx_set_cert_verify_callback(3). The following descriptions apply in the case of the built-in procedure. An application provided procedurealso has access to the verify depth information and the verify_callback() function, but the way this information is used may be different.

SSL_CTX_set_verify_depth() and SSL_set_verify_depth() set the limit up to which depth certificates in a chain are used during the verificationprocedure. If the certificate chain is longer than allowed, the certificates above the limit are ignored. Error messages are generated as if these certificateswould not be present, most likely a X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY will be issued. The depth count is 'level 0:peer certificate', 'level 1:CA certificate', 'level 2: higher level CA certificate', and so on. Setting the maximum depth to 2 allows the levels 0, 1, and 2.The default depth limit is 9, allowing for the peer certificate and additional 9 CA certificates.

The verify_callback function is used to control the behaviour when the SSL_VERIFY_PEER flag is set. It must be supplied by theapplication and receives two arguments: preverify_ok indicates, whether the verification of the certificate in question was passed (preverify_ok=1) ornot (preverify_ok=0). x509_ctx is a pointer to the complete context used for the certificate chain verification.

The certificate chain is checked starting with the deepest nesting level (the root CA certificate) and worked upward to the peer'scertificate. At each level signatures and issuer attributes are checked. Whenever a verification error is found, the error number is stored in x509_ctxand verify_callback is called with preverify_ok=0. By applying X509_CTX_store_* functions verify_callback can locate the certificate inquestion and perform additional steps (see EXAMPLES ). If no error is found for a certificate, verify_callback is called withpreverify_ok=1 before advancing to the next level.

The return value of verify_callback controls the strategy of the further verification process. If verify_callback returns 0, the verificationprocess is immediately stopped with 'verification failed' state. If SSL_VERIFY_PEER is set, a verification failure alert is sent to the peer andthe TLS/SSL handshake is terminated. If verify_callback returns 1, the verification process is continued. If verify_callbackalways returns 1, the TLS/SSL handshake will not be terminated with respect to verification failures and the connection will be established. Thecalling process can however retrieve the error code of the last verification error using ssl_get_verify_result(3) or by maintaining its own errorstorage managed by verify_callback.

If no verify_callback is specified, the default callback will be used. Its return value is identical to preverify_ok, so that any verificationfailure will lead to a termination of the TLS/SSL handshake with an alert message, if SSL_VERIFY_PEER is set.

Bugs

In client mode, it is not checked whether the SSL_VERIFY_PEER flag is set, but whether SSL_VERIFY_NONE is not set. This canlead to unexpected behaviour, if the SSL_VERIFY_PEER and SSL_VERIFY_NONE are not used as required (exactly one must be set at anytime).

The certificate verification depth set with SSL[_CTX]_verify_depth() stops the verification at a certain depth. The error message produced will bethat of an incomplete certificate chain and not X509_V_ERR_CERT_CHAIN_TOO_LONG as may be expected.

Return Values

The SSL*_set_verify*() functions do not provide diagnostic information.

Examples

The following code sequence realizes an example verify_callback function that will always continue the TLS/SSL handshake regardless ofverification failure, if wished. The callback realizes a verification depth limit with more informational output.

X509_store_add_cert

All verification errors are printed, informations about the certificate chain are printed on request. The example is realized for a server that does allowbut not require client certificates.

Man X509_store_add_cert

The example makes use of the ex_data technique to store application data into/retrieve application data from the SSL structure (seessl_get_ex_new_index(3), ssl_get_ex_data_x509_store_ctx_idx(3)).

See Also

ssl(3), ssl_new(3), ssl_ctx_get_verify_mode(3), ssl_get_verify_result(3), ssl_ctx_load_verify_locations(3),ssl_get_peer_certificate(3), ssl_ctx_set_cert_verify_callback(3), ssl_get_ex_data_x509_store_ctx_idx(3),ssl_get_ex_new_index(3)

Referenced By

cp_httpsocket(3),cp_socket(3),ssl_ctx_set_cert_store(3),ssl_set_max_cert_list(3)
  • Status:Closed
  • Resolution: Duplicate
  • Fix Version/s: None
  • Labels:
  • Environment:

Occasionally I get the following error causing mongoimport / mongorestore to fail. Is there a workaround for this? I am running this against an atlas cluster. These tools are used as part of automated script. Is my only option to retry until it succeeds?

2019-01-18T12:56:58.591-0500 Failed: SSL errors: b07c065:x509 certificate routines:X509_STORE_add_cert:cert already in hash table
b07c065:x509 certificate routines:X509_STORE_add_cert:cert already in hash table
b07c065:x509 certificate routines:X509_STORE_add_cert:cert already in hash table
b07c065:x509 certificate routines:X509_STORE_add_cert:cert already in hash table
b07c065:x509 certificate routines:X509_STORE_add_cert:cert already in hash table
b07c065:x509 certificate routines:X509_STORE_add_cert:cert already in hash table

I do see another bug reported [ https://jira.mongodb.org/browse/TOOLS-1906 ], but its been open for over a year.

X509_store_add_cert Openssl

duplicates

X509store Add Certificate

TOOLS-1906Ignore mongorestore error 'x509 certificate routines:X509_STORE_add_cert:cert already in hash table'

  • Closed

X509_store_add_cert

Votes:
0Vote for this issue
Watchers:
2Start watching this issue