|author||David Benjamin <email@example.com>||Thu Mar 08 13:37:37 2018 -0500|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Thu Mar 08 21:53:06 2018 +0000|
Fix 20-year-old typo in BN_mask_bits. This clearly was supposed to be a return 1. See https://github.com/openssl/openssl/issues/5537 for details. (Additionally, now that our BIGNUMs may be non-minimal, this function violates the rule that BIGNUM functions should not depend on widths. We should use w >= bn_minimal_width(a) to retain the original behavior. But the original behavior is nuts, so let's just fix it.) Update-Note: BN_mask_bits no longer reports failure in some cases. These cases were platform-dependent and not useful, and code search confirms nothing was relying on it. Change-Id: I31b1c2de6c5de9432c17ec3c714a5626594ee03c Reviewed-on: https://boringssl-review.googlesource.com/26464 Commit-Queue: Steven Valdez <firstname.lastname@example.org> Reviewed-by: Steven Valdez <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.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: