commit | cef9d3f38d72f13412c79157c25753e22cb05f7e | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Fri Jun 14 14:09:35 2019 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Jun 14 22:00:47 2019 +0000 |
tree | 86d59f7de4f77a359efc5693b91ea22d5a941790 | |
parent | 8f574c37dae935a29bff56e750101e5b354503de [diff] |
Split p224-64.c multiplication functions in three. See I9c20b660ce4b58dc633588cfd5b2e97a40203ec3 for motivation. This aligns with the other curves. In doing so, I removed the constant-time table lookups from mul_public because it was easy, which gave a small performance improvement. I did not further use ec_compute_wNAF, on the assumption that we do not care enough about P-224 ECDSA performance to bother. Before: Did 63756 ECDSA P-224 verify operations in 5032477us (12668.9 ops/sec) After: Did 71914 ECDSA P-224 verify operations in 5042356us (14262.0 ops/sec) [+12.5%] Change-Id: Ifd20293aca09e578c85d4692294caffc1b287909 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/36464 Commit-Queue: David Benjamin <davidben@google.com> 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: