commit | d103616db14ca9587f074efaf9f09a48b8ca80cb | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Thu Jan 26 09:55:07 2017 -0500 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jan 26 18:29:44 2017 +0000 |
tree | 1562f45183030a806acef07fa7a12161f7a36cdd | |
parent | 47383aadffdd80b5a8d4e4fa4b172a1a25dbd376 [diff] |
bn/asm/x86_64-mont5.pl: fix carry bug in bn_sqr8x_internal. CVE-2017-3732 (Imported from upstream's 3f4bcf5bb664b47ed369a70b99fac4e0ad141bb3 and 3e7a496307ab1174c1f8f64eed4454c1c9cde1a8.) Change-Id: I40255fdf4184e3b919758a72c3d3a7486d91ff65 Reviewed-on: https://boringssl-review.googlesource.com/13360 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: