| commit | ad5e3e3597f98bca70b2f2e11dc439000d092a44 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Apr 06 17:45:47 2020 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Apr 07 23:46:10 2020 +0000 |
| tree | 6bf71ad4bf3513211bd24f9b9f2b13b65ca7530f | |
| parent | 58add794d995e0462afbfea92d28fc2f4e38a10e [diff] |
Remove BIGNUM from uncompressed coordinate parsing. Compressed coordinates still use BIGNUM. I've moved the curve check to an EC_FELEM-based ec_point_set_affine_coordinates and implemented a tighter one than ec_GFp_simple_is_on_curve, which currently needs to branch on Jacobian vs. affine and potentially leaks information. (A later CL will make it conservatively always perform a Jacobian check.) The Trust Tokens implementation will eventually need to deserialize points, so this avoids needing to allocate EC_POINTs everywhere. Likewise if we ever get around to adding a better ECDH, this will let us avoid pulling in BIGNUMs. Bug: chromium:1014199, 242 Change-Id: I93162ba3680d38cb3c0eacff1eb8f42a445246ea Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/40587 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.
Project links:
There are other files in this directory which might be helpful: