| commit | 9b602f2d911db5c528bb9832256477bf63584260 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Aug 14 18:08:32 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 21 15:06:00 2025 -0700 |
| tree | 10a7160cb2bc5e6a9ea258992794c4ab7126b277 | |
| parent | 4d48736c2acd6878caa93ac0a628b46bda1227b0 [diff] |
Limit EVP_PKEY_set_type to EVP_PKEY_X25519 Per the docs, the only real use case is setting EVP_PKEY_X25519. Outside BoringSSL, the one caller using other key types to make test keys has since been fixed. One call to EVP_PKEY_set_type(EVP_PKEY_NONE) remains, but this CL does not break it. This removes one path to making this flavor of half-empty keys for all but X25519, where we're forced to have such keys for OpenSSL compatibility. Update-Note: EVP_PKEY_set_type will now only succeed for EVP_PKEY_X25519. EVP_PKEY_set_type(EVP_PKEY_NONE) will continue to clear the pkey and then fail. Going through code search, there are not expected to be any affected callers. Bug: 42290409 Change-Id: I20ca762be71f71a628f5894045e5b66b7773c215 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81548 Reviewed-by: Lily Chen <chlily@google.com> Commit-Queue: Lily Chen <chlily@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: