b9940a649a
Close difference gap on Cortex-A9, which resulted in further improvement even on other processors. (Imported from upstream's 8eed3289b21d25583ed44742db43a2d727b79643.) Performance numbers on a Nexus 5X in AArch32 mode: $ ./bssl.old speed -filter RSA -timeout 5 Did 355 RSA 2048 signing operations in 5009578us (70.9 ops/sec) Did 20577 RSA 2048 verify operations in 5079000us (4051.4 ops/sec) Did 66 RSA 4096 signing operations in 5057941us (13.0 ops/sec) Did 5564 RSA 4096 verify operations in 5086902us (1093.8 ops/sec) $ ./bssl speed -filter RSA -timeout 5 Did 411 RSA 2048 signing operations in 5010206us (82.0 ops/sec) Did 27720 RSA 2048 verify operations in 5048114us (5491.2 ops/sec) Did 86 RSA 4096 signing operations in 5056160us (17.0 ops/sec) Did 8216 RSA 4096 verify operations in 5048719us (1627.3 ops/sec) Change-Id: I8c5be9ff9405ec1796dcf4cfe7df8a89e5a50ce5 Reviewed-on: https://boringssl-review.googlesource.com/17109 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.