| commit | 92f888e8362e2965f8658c911041f7794ad93b5e | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Tue Apr 11 15:06:47 2017 -0700 |
| committer | Adam Langley <agl@google.com> | Fri Apr 14 16:55:49 2017 +0000 |
| tree | 9a7c56c3bdfbaacc00c790f58f1ef16ca43af4de | |
| parent | 88bb8489dbb307699ac8967ef65bb9c38f02ebd1 [diff] |
Make fork-unsafe buffering act via CTR-DRBG. Fork-unsafe buffering was a mode that could be enabled by applications that were sure that they didn't need to worry about state duplication. It saved reads to urandom. Since everything is now going through the CTR-DRBG, we can get the same effect by simply not reading additional data from urandom in this case. This change drops the buffering from urandom.c and, instead, implements fork-unsafe buffering as a mode that skips reading additional data from urandom, which only happened when RDRAND wasn't available anyway. Since we expect the power-on self-tests to call into the PRNG, this change also makes the flag capable of changing at any point by using a mutex rather than a once. This is split into a separate file so that it doesn't have to go into the FIPS module—since it uses r/w data that would be a pain. Change-Id: I5fd0ead0422e770e35758f080bb1cffa70d0c8da Reviewed-on: https://boringssl-review.googlesource.com/14924 Reviewed-by: Adam Langley <agl@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: