a0f1c8e3b1
On a Skylake machine, the improvements to make RSA key generation constant-time did slow things down a bit: Before: Did 217 RSA 2048 key-gen operations in 30231344us (7.2 ops/sec) min: 17154us, median: 117284us, max: 518336us Did 70 RSA 3072 key-gen operations in 30188611us (2.3 ops/sec) min: 57759us, median: 348873us, max: 1760351us Did 27 RSA 4096 key-gen operations in 30264235us (0.9 ops/sec) min: 202096us, median: 980160us, max: 4282915us After: Did 186 RSA 2048 key-gen operations in 30021173us (6.2 ops/sec) min: 74850us, median: 147650us, max: 407031us Did 54 RSA 3072 key-gen operations in 30111667us (1.8 ops/sec) min: 292050us, median: 483786us, max: 1294105us Did 18 RSA 4096 key-gen operations in 30662495us (0.6 ops/sec) min: 902547us, median: 1446689us, max: 3660302us Change-Id: I52a96bb41bab759aa7ef6239bdfa533707a9eb3c Reviewed-on: https://boringssl-review.googlesource.com/26904 Commit-Queue: Adam Langley <alangley@gmail.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
|---|---|---|
| .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.