|author||Adam Langley <firstname.lastname@example.org>||Wed Sep 05 14:09:52 2018 -0700|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Fri Dec 28 18:05:18 2018 +0000|
Use thread-local storage for PRNG states if fork-unsafe buffering is enabled. We switched from thread-local storage to a mutex-pool in 82639e6f53 because, for highly-threaded processes, the memory used by all the states could be quite large. I had judged that a mutex-pool should be fine, but had underestimated the PRNG requirements of some of our jobs. This change makes rand.c support using either thread-locals or a mutex-pool. Thread-locals are used if fork-unsafe buffering is enabled. While not strictly related to fork-safety, we already have the fork-unsafe control, and it's already set by jobs that care a lot about PRNG performance, so fits quite nicely here. Change-Id: Iaf1e0171c70d4c8dbe1e42283ea13df5b613cb2d Reviewed-on: https://boringssl-review.googlesource.com/c/31564 Commit-Queue: Adam Langley <email@example.com> Reviewed-by: David Benjamin <firstname.lastname@example.org>
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: