| commit | 6544426d82a98f489c25acc5f2ca84f3ed79a0ef | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@chromium.org> | Tue Dec 22 11:41:13 2015 -0500 |
| committer | Adam Langley <agl@google.com> | Tue Dec 22 23:30:22 2015 +0000 |
| tree | 230e01a9806d3fe17a953e7616acaa4f01675591 | |
| parent | fe5f7c7b56e1d54478d2983c26153ead80e0322a [diff] |
Fix a ** 0 mod 1 = 0 for real this time. Commit 2b0180c37fa6ffc48ee40caa831ca398b828e680 attempted to do this but only hit one of many BN_mod_exp codepaths. Fix remaining variants and add a test for each method. Thanks to Hanno Boeck for reporting this issue. (Imported from upstream's 44e4f5b04b43054571e278381662cebd3f3555e6.) Change-Id: Ic691b354101c3e9c3565300836fb6d55c6f253ba Reviewed-on: https://boringssl-review.googlesource.com/6820 Reviewed-by: Adam Langley <agl@google.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: