commit | 8618f2bfe0f9e83127e5a3f9238ba5fe2268ae44 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Fri Nov 09 16:46:55 2018 -0600 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Nov 13 01:48:21 2018 +0000 |
tree | 55885cbdfc3a4a1c196ab351b1b2298caac13723 | |
parent | 0b3f497bcd4ad79a565b2d71c2d8de9b77ce1040 [diff] |
Optimize EC_GFp_mont_method's cmp_x_coordinate. For simplicity, punt order > field or width mismatches. Analogous optimizations are possible, but the generic path works fine and no commonly-used curve looks hits those cases. Before: Did 5888 ECDSA P-384 verify operations in 3094535us (1902.7 ops/sec) After [+6.7%]: Did 6107 ECDSA P-384 verify operations in 3007515us (2030.6 ops/sec) Also we can fill in p - order generically and avoid extra copies of some constants. Change-Id: I38e1b6d51b28ed4f8cb74697b00a4f0fbc5efc3c Reviewed-on: https://boringssl-review.googlesource.com/c/33068 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Adam Langley <agl@google.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: