OpenSSL 1.1.0 *does not* go through the locking callbacks. They will never be
called.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
ssl.org Subject: Re: [openssl-users] Should I stop using
locking callbacks in OpenSSL 1.1.0x ?
Does this mean I can safely remove all usages of the above functions from my
application code? I'd appreciate if someone could explain
the above comment in a little more detail or confirm wha
* Does this mean I can safely remove all usages of the above functions from
my application code? I'd appreciate if someone could explain the above comment
in a little more detail or confirm what I'm saying. Or has anyone else been in
the same situation?
Yes. Do not use the locking callba
Hi all,
I'm trying to migrate some application code from OpenSSL 1.0.1e to 1.1.0g.
I keep seeing that the locking and threading callbacks I had used earlier
(with CRYPTO_set_locking_callback and CRYPTO_set_id_callback respectively)
now show up as "unused" during compilation.
I checked https://www