| commit | 33f3ee8b6b615f0211b12073b266ff04e2963025 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <alangley@gmail.com> | Tue May 10 10:15:31 2022 -0700 |
| committer | Adam Langley <agl@google.com> | Wed Jul 27 07:08:23 2022 +0000 |
| tree | ac64326ae65278a8877482250b8cd81df7fcaf1f | |
| parent | 4a6c8fde1807094d0dcdbdcb48206e3736e1b272 [diff] |
Rename |from_cpu| to |want_additional_input|. This flag is currently set if DRBG entropy is obtained from RDRAND. It indicates that we should add kernel entropy when seeding the DRBG. But this might be true for methods other than RDRAND in the future so this change renames it accordingly. Change-Id: I91826178a806e3c6dadebbb844358a7a12e0b09b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/52525 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.
Project links:
There are other files in this directory which might be helpful: