e.g. a store has a X509_VERIFY_PARAMS field, however although an
SSL_CTX* has a related store, it ignores the store's params and uses
For a connection pooling implementation, I need to check that an
existing SSL connection is something that could be approved by a given
I was hoping this would be as simple as doing (error handling omitted
// X509_STORE_CTX_set_verify_cb based on SSL_CTX_get_verify_callback(ctx)
// etc. etc.
Is this complexity warranted?
Is there any plan to remove the redundant fields?