| commit | e6bf9065afbe6a9d4762c8e23f47eb7b8ecaad07 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Thu Jan 03 08:51:34 2019 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jan 03 20:19:44 2019 +0000 |
| tree | 98f899405894c339cf26ed5da33d9704dc07c2f2 | |
| parent | 7177c1d29fdb87a260a0510f815828cb02db99be [diff] |
Remove pooling of PRNG state. Prior to 82639e6f we used thread-local data for the PRNG state. That change switched to using a mutex-protected pool instead in order to save memory in heavily-threaded applications. However, the pool mutex can get extremely hot in cases where the PRNG is heavily used. 8e8f2504 was a short-term work around, but supporting both modes is overly complex. This change moves back to the state of the prior to 82639e6f. The best way to review this is to diff the changed files against '82639e6f^' and note that the only difference is a comment added in rand.c: https://paste.googleplex.com/4997991748337664 Change-Id: I8febce089696fa6bc39f94f4a1e268127a8f78db Reviewed-on: https://boringssl-review.googlesource.com/c/34024 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: David Benjamin <davidben@google.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
There are other files in this directory which might be helpful: