| commit | 25f3d84f4cf1f92c9fb44e4b93c3ade41bdf968c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Feb 04 11:09:50 2018 -0500 |
| committer | Adam Langley <agl@google.com> | Mon Apr 02 18:07:12 2018 +0000 |
| tree | 14597043f89b79276bca5190daf11e2dfdf477c3 | |
| parent | 85c2cd8a458dc62fb7e9a540d94d21d1bb39c86a [diff] |
Rewrite BN_rand without an extra malloc. RSA keygen uses this to pick primes. May as well avoid bouncing on malloc. (The BIGNUM internally allocates, of course, but that allocation will be absorbed by BN_CTX in RSA keygen.) Change-Id: Ie2243a6e48b9c55f777153cbf67ba5c06688c2f1 Reviewed-on: https://boringssl-review.googlesource.com/26887 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: