|author||Brian Smith <email@example.com>||Tue Nov 17 21:57:01 2015 -1000|
|committer||Adam Langley <firstname.lastname@example.org>||Thu Nov 19 01:39:32 2015 +0000|
s/BN_BITS/BN_BITS2/ in |BN_mod_inverse_ex|; remove |BN_BITS| & |BN_MASK|. The comment in |BN_mod_inverse_ex| makes it clear that |BN_BITS2| was intended. Besides fixing the code to match the comment, remove the now-unused |BN_BITS| and the already-unused |BN_MASK| to prevent future confusion of this sort. On MSVC builds there seems to be very little difference in performance between the two code paths according to |bssl speed|. Change-Id: I765b7b3d464e2057b1d7952af25b6deb2724976a Reviewed-on: https://boringssl-review.googlesource.com/6525 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: