On Mon, Sep 30, 2013, nehakochar wrote: > > It should never happen in practice unless something bad has happened such > as > > memory corruption. For example there is a variable which simulates a > > failure > > of the test which might be overwritten if something writes over memory. > > It is not memory corruption from what I see. I had added a log when memcmp > would fail, and that's what I see. So, the memcmp is indeed failing. >
Can it happen soon after start up or does it seems to require a large number of operations before it happens? I'm wondering if it might be associated with reseeding. > Is this DRBG code thread-safe? If it isn't, then that could be the cause. > It should be thread safe if the locks are set properly. The generation operation takes place under CRYPTO_LOCK_RAND. If the locking doesn't work properly then race conditions could corrupt the internal state which might cause what you are seeing. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
