|author||David Benjamin <email@example.com>||Sat Jan 27 18:54:28 2018 -0500|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Tue Feb 06 03:10:44 2018 +0000|
Make BN_cmp constant-time. This is a bit easier to read than BN_less_than_consttime when we must do >= or <=, about as much work to compute, and lots of code calls BN_cmp on secret data. This also, by extension, makes BN_cmp_word constant-time. BN_equal_consttime is probably a little more efficient and is perfectly readable, so leave that one around. Change-Id: Id2e07fe312f01cb6fd10a1306dcbf6397990cf13 Reviewed-on: https://boringssl-review.googlesource.com/25444 Commit-Queue: David Benjamin <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <firstname.lastname@example.org> 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: