commit | 41eb357d05e1603a15b23c4c7f21b5240664453a | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Sat Nov 12 12:30:50 2022 +0000 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Nov 14 17:02:34 2022 +0000 |
tree | d060e28002831334c14b0ce18350e77e27d68e38 | |
parent | 0faffc7a30eeb195248ea43056f4848e2a9b1c6d [diff] |
Do not allow changing keys with parameters already set. This aligns with upstream's f72f00d49549c6620d7101f5e9bf7963da6df9ee. In doing so, I had to fill in a bunch of NULL checks in p_ec_asn1.c, to account for EVP's needlessly many "empty" states. For now, those cases return a goofy -2 to align with upstream. Our EVP_PKEY_cmp_parameters still returns negative values, so this is fine, though ideally we'd narrow to boolean. That probably depends on some other changes. See https://crbug.com/boringssl/536#c3. Bug: 536 Change-Id: I1124c8ad5223ac23953d94ff9ca734fbb714e89c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/55185 Reviewed-by: Bob Beck <bbe@google.com> Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@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: