| commit | 55761e68024235578cd2fd5fc17bd64a5d8a7c9c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Nov 03 15:24:36 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Nov 03 19:37:31 2017 +0000 |
| tree | fb6d5862dee9500d224df0c19bcab0ec9f771a20 | |
| parent | 431e767c23a238378e7300525075c2d24cd5c73b [diff] |
Use a higher iteration limit for RSA key generation at e = 3. Generating a 2048-bit RSA key with e = 3 (don't do this), the failure rate at 5*bits iterations appears to be around 7 failures in 1000 tries. Bump the limit up to 32*bits. This should give a failure rate of around 2 failures in 10^14 tries. (The FIPS 186-4 algorithm is meant for saner values of e, like 65537. e = 3 implies a restrictive GCD requirement: the primes must both be 2 mod 3.) Change-Id: Icd373f61e2eb90df5afaff9a0fc2b2fbb6ec3f0a Reviewed-on: https://boringssl-review.googlesource.com/22584 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: 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: