|author||David Benjamin <firstname.lastname@example.org>||Mon May 11 17:43:57 2020 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue May 12 17:38:55 2020 +0000|
Use public multi-scalar mults in Trust Tokens where applicable. The input points are all public, so we can use a faster multi-scalar multiplication. This generalizes ec_point_mul_scalar_public to ec_point_mul_scalar_public_batch. To support the batched DLEQ construction, this function takes an arbirarily-length array of points and allocates some temporaries if necessary. First, to confirm that this doesn't affect the basic ECDSA verify case: Before: Did 6324 ECDSA P-384 verify operations in 3069342us (2060.4 ops/sec) After: Did 6324 ECDSA P-384 verify operations in 3063355us (2064.4 ops/sec) [+0.2%] Results for Trust Tokens issue (Exp1) and finish_issuance (both): Before: Did 147 TrustToken-Exp0-Batch1 finish_issuance operations in 2059145us (71.4 ops/sec) Did 14 TrustToken-Exp0-Batch10 finish_issuance operations in 2085888us (6.7 ops/sec) Did 357 TrustToken-Exp1-Batch1 issue operations in 2068238us (172.6 ops/sec) Did 286 TrustToken-Exp1-Batch1 finish_issuance operations in 2090932us (136.8 ops/sec) Did 63 TrustToken-Exp1-Batch10 issue operations in 2068201us (30.5 ops/sec) Did 56 TrustToken-Exp1-Batch10 finish_issuance operations in 2064796us (27.1 ops/sec) After: Did 168 TrustToken-Exp0-Batch1 finish_issuance operations in 2058891us (81.6 ops/sec) [+14.3%] Did 16 TrustToken-Exp0-Batch10 finish_issuance operations in 2075742us (7.7 ops/sec) [+14.8%] Did 378 TrustToken-Exp1-Batch1 issue operations in 2067956us (182.8 ops/sec) [+5.9%] Did 336 TrustToken-Exp1-Batch1 finish_issuance operations in 2097757us (160.2 ops/sec) [+17.1%] Did 105 TrustToken-Exp1-Batch10 issue operations in 2069934us (50.7 ops/sec) [+66.5%] Did 88 TrustToken-Exp1-Batch10 finish_issuance operations in 2014621us (43.7 ops/sec) [+61.1%] (This CL doesn't affect other operations.) Change-Id: Ie643b06f44990ab52bf892a007732fde61cdffe5 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/41285 Reviewed-by: Steven Valdez <email@example.com> Commit-Queue: David Benjamin <firstname.lastname@example.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: