|
|
|
|
|
by sdrapkin
4018 days ago
|
|
I have verified that the CryptoRandom class is part of a standalone library with (1) should be thread-safe since it cannot dictate how it will be used by callers; (2) the authors clearly intended this library to be thread-safe (based on "thread-safe" comments in its source code). And in all likelihood it is thread-safe - but that's due to being lucky - not competent. The larger issue is that we have a widely-used crypto software which is clearly (1) not designed well; (2) not implemented well. How much trust one is willing to place into current and future versions by the same author(s) is up to you. |
|
But "(2) the authors clearly intended this library to be thread-safe" means that piece of code is bad. So you have a point here.