Go to file
Adam Langley 8e8f250422 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 <agl@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
2018-12-28 18:05:18 +00:00
.github
crypto Use thread-local storage for PRNG states if fork-unsafe buffering is enabled. 2018-12-28 18:05:18 +00:00
decrepit Undo recent changes to |X509V3_EXT_conf_nid|. 2018-10-17 21:05:45 +00:00
fipstools Support symbol prefixes 2018-09-06 20:07:52 +00:00
fuzz Refresh fuzzer corpora for changes to split-handshake serialization. 2018-11-06 01:19:38 +00:00
include/openssl Use thread-local storage for PRNG states if fork-unsafe buffering is enabled. 2018-12-28 18:05:18 +00:00
infra/config No longer set CQ-Verified label on CQ success/failure. 2018-11-19 16:59:05 +00:00
ssl Use same HKDF label as TLS 1.3 for QUIC as per draft-ietf-quic-tls-17 2018-12-19 20:25:34 +00:00
third_party Modernize OPENSSL_COMPILE_ASSERT, part 2. 2018-11-14 16:06:37 +00:00
tool HRSS: omit reconstruction of ciphertext. 2018-12-19 20:09:34 +00:00
util Drop NEON assembly for HRSS. 2018-12-13 17:43:07 +00:00
.clang-format
.gitignore Update tools. 2018-09-13 17:57:30 +00:00
API-CONVENTIONS.md Clarify "reference" and fix typo. 2018-09-05 19:06:48 +00:00
BREAKING-CHANGES.md
BUILDING.md Switch docs to recommending NASM. 2018-11-14 16:00:42 +00:00
CMakeLists.txt Add start of infrastructure for checking constant-time properties. 2018-12-18 22:43:02 +00:00
codereview.settings
CONTRIBUTING.md
FUZZING.md Switch to Clang 6.0's fuzzer support. 2018-08-27 17:18:56 +00:00
go.mod Set up Go modules. 2018-09-17 21:04:17 +00:00
INCORPORATING.md Update URL for GN quick start guide. 2018-08-16 20:18:41 +00:00
LICENSE
PORTING.md
README.md
sources.cmake Add new curve/hash ECDSA combinations from Wycheproof. 2018-08-10 18:26:06 +00:00
STYLE.md

BoringSSL

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: