|author||David Benjamin <email@example.com>||Tue Nov 14 07:58:16 2017 +0800|
|committer||Adam Langley <firstname.lastname@example.org>||Wed Nov 22 22:52:04 2017 +0000|
Use some of the word-based functions for ECDSA verification. This is only a hair faster than the signing change, but still something. I kept the call to BN_mod_inverse_odd as that appears to be faster (constant time is not a concern for verification). Before: Did 22855 ECDSA P-224 verify operations in 3015099us (7580.2 ops/sec) Did 21276 ECDSA P-256 verify operations in 3083284us (6900.4 ops/sec) Did 2635 ECDSA P-384 verify operations in 3032582us (868.9 ops/sec) Did 1240 ECDSA P-521 verify operations in 3068631us (404.1 ops/sec) After: Did 23310 ECDSA P-224 verify operations in 3056226us (7627.1 ops/sec) Did 21210 ECDSA P-256 verify operations in 3035765us (6986.7 ops/sec) Did 2666 ECDSA P-384 verify operations in 3023592us (881.7 ops/sec) Did 1209 ECDSA P-521 verify operations in 3054040us (395.9 ops/sec) Change-Id: Iec995b1a959dbc83049d0f05bdc525c14a95c28e Reviewed-on: https://boringssl-review.googlesource.com/23077 Reviewed-by: Adam Langley <email@example.com>
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: