crypto/asn1/x_req.c, line 105:
ASN1_SEQUENCE_ref(X509_REQ, 0, CRYPTO_LOCK_X509_INFO)
I think CRYPTO_LOCK_X509_INFO should be replaced with
CRYPTO_LOCK_X509_REQ so that the lock naming is consistent with X509 and
X509_CRL. This avoids confusion (and potential bugs) when using
CRYPTO_add to
Hello,
Over the past few days I have managed to put together a regression
testing framework for OpenSSL that allows test cases to be created to
synthetically setup a specific application, OpenSSL and networking layer
interaction scenario (and validate for expected error returns, or ensure
a
