fb8b763e51
FIPS prescribes a slightly different key generation algorithm than we use. Specifically: - Rather than using BN_RAND_TOP_TWO (so using 1.5 as an upper bound for sqrt(2)), it prescribes using sqrt(2) itself. To avoid unnecessary squaring, we do a comparison against a hard-coded approximation for sqrt(2) good enough for the largest FIPS key size. I went ahead and made it constant-time since it was easy, but all this is far from constant-time. - FIPS requires a check that |p-q| is sufficiently large. - FIPS requires a check that d is sufficiently large. - BN_generate_prime_ex adds some delta to clear a table of prime numbers. FIPS does not specify any of that, so implement a separate routine here. The primality test itself will be aligned in a follow-up. For now, it is left unchanged, except that trial division is turned back on. That makes things faster and is analogous the original algorithm's delta-munging logic. Change-Id: If32f0635bfb67a8c4740dedd7781d00647bbf60b Reviewed-on: https://boringssl-review.googlesource.com/14948 Reviewed-by: Adam Langley <agl@google.com> |
||
|---|---|---|
| .github | ||
| crypto | ||
| decrepit | ||
| fuzz | ||
| include/openssl | ||
| infra/config | ||
| ssl | ||
| third_party | ||
| tool | ||
| util | ||
| .clang-format | ||
| .gitignore | ||
| API-CONVENTIONS.md | ||
| BUILDING.md | ||
| CMakeLists.txt | ||
| codereview.settings | ||
| CONTRIBUTING.md | ||
| FUZZING.md | ||
| INCORPORATING.md | ||
| LICENSE | ||
| PORTING.md | ||
| README.md | ||
| STYLE.md | ||
BoringSSL
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:
- PORTING.md: how to port OpenSSL-using code to BoringSSL.
- BUILDING.md: how to build BoringSSL
- INCORPORATING.md: how to incorporate BoringSSL into a project.
- API-CONVENTIONS.md: general API conventions for BoringSSL consumers and developers.
- STYLE.md: rules and guidelines for coding style.
- include/openssl: public headers with API documentation in comments. Also available online.
- FUZZING.md: information about fuzzing BoringSSL.
- CONTRIBUTING.md: how to contribute to BoringSSL.