Gratuitous gcry_fast_random_poll

Werner Koch wk at
Wed May 5 20:36:09 CEST 2004

On Wed, 05 May 2004 19:35:34 +0200, Marcus Brinkmann said:

> The asserts in the code check if the proper lock/unlock calls are made
> in the single-threaded case, too.

Which is a Good Thing.

> If the locking interface is exported in gcrypt, and users are
> responsible for their own locking, these assertions should probably be
> removed.

Why?  Calling ath_mutex_lock on a locked mutex is a severe error in
any case.


More information about the Gcrypt-devel mailing list