commit | 4d48736c2acd6878caa93ac0a628b46bda1227b0 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue Aug 19 16:36:32 2025 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 21 14:42:26 2025 -0700 |
tree | 4a77f9ac211ea7bfea346a8c5d67acdebb448a27 | |
parent | 5dc17fad959038213a36baac6e2f46b5735baf32 [diff] |
Add a test that arbitrary curves can be wrapped in EVP_PKEY Conscrypt relies on both this working at the EC_KEY level, but also EVP_PKEY. Make sure this keeps working, even as we mess around with EVP_PKEY's EC bits to separate the curves out. While I'm here, move the common HexToBIGNUM wrapper into test_util.h. Bug: 42290364 Change-Id: I58fa5a8487b8a499000a798040a53fc851b0a732 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81547 Reviewed-by: Lily Chen <chlily@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: