Since ssleay_rand_initialize() unlocks then locks CRYPTO_LOCK_RAND,
authorRichard Levitte <levitte@openssl.org>
Wed, 29 Mar 2000 17:25:52 +0000 (17:25 +0000)
committerRichard Levitte <levitte@openssl.org>
Wed, 29 Mar 2000 17:25:52 +0000 (17:25 +0000)
commit7ae634de49b58283dd239a13d26296f10f07a325
treec2e2c23fef32e58991d80e5bb657624d61a1f599
parent8311d323783dfdd52ec87cf0429ec67bc21965a1
Since ssleay_rand_initialize() unlocks then locks CRYPTO_LOCK_RAND,
it's a good thing if ssleay_rand_status() would do the corresponding
lock and unlock as everyone else...
crypto/rand/md_rand.c