|author||David Benjamin <firstname.lastname@example.org>||Thu Nov 02 11:02:46 2017 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Nov 02 17:07:57 2017 +0000|
bn/asm/x86_64-mont5.pl: fix carry bug in bn_sqrx8x_internal. Credit to OSS-Fuzz for finding this. CVE-2017-3736 (Imported from upstream's 668a709a8d7ea374ee72ad2d43ac72ec60a80eee and 420b88cec8c6f7c67fad07bf508dcccab094f134.) This bug does not affect BoringSSL as we do not enable the ADX code. Note the test vector had to be tweaked to take things in and out of Montgomery form. (There may be something to be said for test vectors for just BN_mod_mul_montgomery, though we'd need separate 64-bit and 32-bit ones because R can be different.) Change-Id: I832070731ac1c5f893f9c1746892fc4a32f023f5 Reviewed-on: https://boringssl-review.googlesource.com/22484 Commit-Queue: Adam Langley <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <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: