diff options
| author | jsing <> | 2018-11-24 04:11:47 +0000 |
|---|---|---|
| committer | jsing <> | 2018-11-24 04:11:47 +0000 |
| commit | b2f89354805a7b9d93880d8953cd132eadedeca4 (patch) | |
| tree | e76987af4d3eff5c5d457887ba61d74f44234bb1 /src/lib/libcrypto/dsa/dsa_sign.c | |
| parent | ab91451e6ebf1260022c78c25a334e437c04d78e (diff) | |
| download | openbsd-b2f89354805a7b9d93880d8953cd132eadedeca4.tar.gz openbsd-b2f89354805a7b9d93880d8953cd132eadedeca4.tar.bz2 openbsd-b2f89354805a7b9d93880d8953cd132eadedeca4.zip | |
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@
Diffstat (limited to 'src/lib/libcrypto/dsa/dsa_sign.c')
0 files changed, 0 insertions, 0 deletions