| commit | d4d501c1596debd165f425b0364c4c678d04c741 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Apr 30 20:23:33 2020 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue May 12 19:24:22 2020 +0000 |
| tree | 4966be672d1c5ca5ab6a05c403a0204131e329b7 | |
| parent | a810d82575ecbde26406fa583371f807f8721ed7 [diff] |
Trim Z coordinates from the OPENSSL_SMALL P-256 tables. The small P-256 tables currently store 2 * 16 points in Jacobian coordinates, but all the Z values are one, except for the two entries which store infinity. Instead, store only affine coordinates and omit the infinity entries. (We can recover infinity with constant-time selects.) This trims 1152 bytes from the table. Comparing the sizes of the bssl tool (stripped, otherwise debug symbols undo the size gain), the binary is 4096 bytes smaller, but I suspect this is just an artifact of something rounding to page sizes. Along the way, I've scripted the table generation and merged it into a much generalized version of make_p256-x86_64-table.go. As a bonus, by cutting the size of the table we scan, it's faster! (ECDSA verify was already not scanning a table, so that one staying the same is expected.) Before: Did 22302 ECDH P-256 operations in 4009795us (5561.9 ops/sec) Did 62000 ECDSA P-256 signing operations in 4020075us (15422.6 ops/sec) Did 26544 ECDSA P-256 verify operations in 4056526us (6543.5 ops/sec) After: Did 23001 ECDH P-256 operations in 4016544us (5726.6 ops/sec) [+3.0%] Did 66000 ECDSA P-256 signing operations in 4043083us (16324.2 ops/sec) [+5.8%] Did 26544 ECDSA P-256 verify operations in 4051220us (6552.1 ops/sec) [+0.1%] Change-Id: Ie88898fd56e57505e3a325c50bbaf0dc5d42eeb3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/41164 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@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.
Project links:
There are other files in this directory which might be helpful: