b8f14b7d53
This is adapted from upstream's eb7916960bf50f436593abe3d5f2e0592d291017. This gives a 22% win for ECDSA signing. (Upstream cites 30-40%, but they are unnecessarily using BN_mod_exp_mont_consttime in their generic path. The exponent is public. I expect part of their 30-40% is just offsetting this.) Did 506000 ECDSA P-256 signing operations in 25044595us (20204.0 ops/sec) Did 170506 ECDSA P-256 verify operations in 25033567us (6811.1 ops/sec) Did 618000 ECDSA P-256 signing operations in 25031294us (24689.1 ops/sec) Did 182240 ECDSA P-256 verify operations in 25006918us (7287.6 ops/sec) Most of the performance win appears to be from the assembly operations and not the addition chain. I have a CL to graft the addition chain onto the C implementation, but it did not show measurable improvement in ECDSA verify. ECDSA sign gets 2-4% faster, but we're more concerned about ECDSA verify in the OPENSSL_SMALL builds. Change-Id: Ide166f98b146c025f7f80ed7906336c16818540a Reviewed-on: https://boringssl-review.googlesource.com/27593 Reviewed-by: Adam Langley <alangley@gmail.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.