On Sat Jul 02 10:59:38 2016, k...@roeckx.be wrote:
> /* Add to some header file */
>
> CRYPTO_RWLOCK *X509_STORE_get_lock(X509_STORE *ctx);
>
> /* Add to some implementation file */
>
> /* Add to crypto/x509/x509_lu.c */
>
> CRYPTO_RWLOCK *X509_STORE_get_lock(X509_STORE *v)
> {
> return v->lock;
> }https://github.com/openssl/openssl/pull/1295 > Repeat for other relevant classes with locks. This has to be considered carefully. For most opaque types, it makes zero sense to give out the lock. However, for opaque types that contain function pointers that leads to user code, I can see scenarios where it does make sense. For this case, I've only considered X509_STORE. -- Richard Levitte levi...@openssl.org -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4602 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
