commit | 7e2a8a34baf87ca12a92cca87b51ee2ee1bfe997 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue Apr 10 17:08:05 2018 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Apr 20 20:37:45 2018 +0000 |
tree | 4d9109b55e9cc527c17ffa4aa16ef5e8e820e3ed | |
parent | b1e6a85443ccaf47c6a2c11b18b090bb0f97eea0 [diff] |
Speed up variable windowed exponentation a bit. The first non-zero window (which we can condition on for public exponents) always multiplies by one. This means we can cut out one Montgomery multiplication. It also means we never actually need to initialize r to one, saving another Montgomery multiplication for P-521. This, in turn, means we don't need the bn_one_to_montgomery optimization for the public-exponent exponentations, so we can delete bn_one_to_montgomery_small. (The function does currently promise to handle p = 0, but this is not actually reachable, so it can just do a reduction on RR.) For RSA, where we're not doing many multiplications to begin with, saving one is noticeable. Before: Did 92000 RSA 2048 verify (same key) operations in 3002557us (30640.6 ops/sec) Did 25165 RSA 4096 verify (same key) operations in 3045046us (8264.2 ops/sec) After: Did 100000 RSA 2048 verify (same key) operations in 3002483us (33305.8 ops/sec) Did 26603 RSA 4096 verify (same key) operations in 3010942us (8835.4 ops/sec) (Not looking at the fresh key number yet as that still needs to be fixed.) Change-Id: I81a025a68d9b0f8eb0f9c6c04ec4eedf0995a345 Reviewed-on: https://boringssl-review.googlesource.com/27286 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: