| commit | 39ae1447592955adfee26444910b4487fd664dcb | [log] [tgz] |
|---|---|---|
| author | Adam Langley <alangley@gmail.com> | Thu Dec 15 15:38:40 2016 -0800 |
| committer | Adam Langley <alangley@gmail.com> | Fri Dec 16 18:21:41 2016 +0000 |
| tree | d48199bb4e0299e92ed4c8e3c24f4dba87747fdd | |
| parent | 16bfff7169dee9d425bae3c01da131087729ccb6 [diff] |
Revert "Revert "crypto/rand: Fix a crash bug in RAND_enable_fork_unsafe_buffering." and "Enable getrandom for entropy gathering."" This reverts commit 97db926cf7e9da7bdf1e52def7101ba8c68786c0, effectively unreverting the two changes that it contained. A subsequent change will fix this code for MSAN. Change-Id: I54a82b667b7a4208c7a960aa28b01cb246bc78c7 Reviewed-on: https://boringssl-review.googlesource.com/12902 Commit-Queue: Adam Langley <alangley@gmail.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: