|author||David Benjamin <firstname.lastname@example.org>||Fri Jan 26 11:18:37 2018 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Feb 06 02:51:54 2018 +0000|
Make bn_mul_part_recursive constant-time. This follows similar lines as the previous cleanups and fixes the documentation of the preconditions. And with that, RSA private key operations, provided p and q have the same bit length, should be constant time, as far as I know. (Though I'm sure I've missed something.) bn_cmp_part_words and bn_cmp_words are no longer used and deleted. Bug: 234 Change-Id: Iceefa39f57e466c214794c69b335c4d2c81f5577 Reviewed-on: https://boringssl-review.googlesource.com/25404 Commit-Queue: David Benjamin <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: