| commit | e7e5a23b4ee7206a5ef935facf4ad28445ff01ca | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Sep 14 13:23:35 2019 -0400 |
| committer | Adam Langley <agl@google.com> | Mon Sep 30 18:03:50 2019 +0000 |
| tree | c0fea73bdc46407841c0cba62f51182073aea49b | |
| parent | 6dfb479755a4a22960dc68efb65e9d061ce1f65f [diff] |
Test some Euler pseudoprimes. The Miller-Rabin test is an extension of the Fermat test (in addition to looking for a^(n-1) != 1, it also looks for a non-trivial square root of unity). It thus seems prudent to sanity-check we indeed reject Fermat pseudoprimes. Euler pseudoprimes are a stronger constraint, so test those. Change-Id: I959769de2da3f8579403621bcf893e7c9247ca33 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37785 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.
Project links:
There are other files in this directory which might be helpful: