|author||David Benjamin <firstname.lastname@example.org>||Thu Jan 25 23:56:35 2018 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Feb 06 02:47:34 2018 +0000|
Make bn_sqr_recursive constant-time. We still need BN_mul and, in particular, bn_mul_recursive will either require bn_abs_sub_words be generalized or that we add a parallel bn_abs_sub_part_words, but start with the easy one. While I'm here, simplify the i and j mess in here. It's patterned after the multiplication one, but can be much simpler. Bug: 234 Change-Id: If936099d53304f2512262a1cbffb6c28ae30ccee Reviewed-on: https://boringssl-review.googlesource.com/25325 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: