|author||David Benjamin <firstname.lastname@example.org>||Tue Mar 20 15:48:41 2018 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Mar 22 16:26:37 2018 +0000|
Test BN_primality test with OEIS A014233 values . These are composite numbers whose composite witnesses aren't in the first however many prime numbers, so deterministically checking small numbers may not work. We don't check composite witnesses deterministically but these are probably decent tests. (Not sure how else to find composites with scarce witnesses, but these seemed decent candidates.) Change-Id: I23dcb7ba603a64c1f7d1e9a16942e7c29c76da51 Reviewed-on: https://boringssl-review.googlesource.com/26645 Commit-Queue: Steven Valdez <email@example.com> Reviewed-by: Steven Valdez <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: