|author||David Benjamin <email@example.com>||Fri Jan 19 09:37:13 2018 -0500|
|committer||Adam Langley <firstname.lastname@example.org>||Fri Feb 02 18:42:39 2018 +0000|
Factor out BN_to_montgomery(1) optimization. This cuts down on a duplicated place where we mess with bn->top. It also also better abstracts away what determines the value of R. (I ordered this wrong and rebasing will be annoying. Specifically, the question is what happens if the modulus is non-minimal. In https://boringssl-review.googlesource.com/c/boringssl/+/25250/, R will be determined by the stored width of mont->N, so we want to use mont's copy of the modulus. Though, one way or another, the important part is that it's inside the Montgomery abstraction.) Bug: 232 Change-Id: I74212e094c8a47f396b87982039e49048a130916 Reviewed-on: https://boringssl-review.googlesource.com/25247 Reviewed-by: Adam Langley <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: