Store and return the locking callbacks, restoring previous behaviour.

The previous code meant that a caller could set the locking callback, after
which CRYPTO_get_locking_callback() would return non-NULL. Some existing
code depends on this behaviour, specifically to identify if lock handling
has been configured. As such, always returning NULL from
CRYPTO_get_locking_callback() can result in unexpected application
behaviour.

ok bcook@

0 files changed, 0 insertions, 0 deletions