| commit | f11ea19043f2b3ee42e4a76d0645914347e1a36e | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Apr 09 20:17:20 2018 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Apr 10 00:58:31 2018 +0000 |
| tree | 0a8dde8d7d4f9cad5e551c297f12fde034f42f86 | |
| parent | bb2e1e1eea7d70492e52878d03f427abc27e358c [diff] |
Actually benchmark RSA verification with a fresh key. https://boringssl-review.googlesource.com/10522 didn't actually do what it was supposed to do. In fact, it appears, not paying attention to it, we've managed to make RSA verify slower than ECDSA verify. Oops. Did 32000 RSA 2048 verify (same key) operations in 1016746us (31473.0 ops/sec) Did 5525 RSA 2048 verify (fresh key) operations in 1067209us (5177.1 ops/sec) Did 8957 ECDSA P-256 verify operations in 1078570us (8304.5 ops/sec) The difference is in setting up the BN_MONT_CTX, either computing R^2 or n0. I'm guessing R^2. The current algorithm needs to be constant-time, but we can split out a variable-time one if necessary. Change-Id: Ie064a0e464aaa803815b56a6734bc9e2becef1a7 Reviewed-on: https://boringssl-review.googlesource.com/27244 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
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: