232a6be6f1
The extra details in Enhanced Rabin-Miller are only used in RSA_check_key_fips, on the public RSA modulus, which the static linker will drop in most of our consumers anyway. Implement normal Rabin-Miller for RSA keygen and use Montgomery reduction so it runs in constant-time. Note that we only need to avoid leaking information about the input if it's a large prime. If the number ends up composite, or we find it in our table of small primes, we can return immediately. The leaks not addressed by this CL are: - The difficulty of selecting |b| leaks information about |w|. - The distribution of whether step 4.4 runs leaks information about w. - We leak |a| (the largest power of two which divides w) everywhere. - BN_mod_word in the trial division is not constant-time. These will be resolved in follow-up changes. Median of 29 RSA keygens: 0m0.521 -> 0m0.621s (Accuracy beyond 0.1s is questionable.) Bug: 238 Change-Id: I0cf0ff22079732a0a3ababfe352bb4327e95b879 Reviewed-on: https://boringssl-review.googlesource.com/25886 Reviewed-by: Adam Langley <agl@google.com> |
||
|---|---|---|
| .github | ||
| crypto | ||
| decrepit | ||
| fipstools | ||
| 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 | ||
| sources.cmake | ||
| 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.