| commit | 729648fb79df7bc46c145e49b0dfd8d2a24232f1 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Aug 15 14:45:08 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 18 16:36:18 2025 -0700 |
| tree | 5ab603a2f21bf2e70032db75322900ed01ae01a1 | |
| parent | 716f066168f585f25010c79b9202e147a5672b46 [diff] |
Rename EVP_R_EXPECTING_AN_EC_KEY_KEY to match OpenSSL EC_KEY_KEY looks very silly. In OpenSSL, this is EVP_R_EXPECTING_A_EC_KEY. It's a little odd that they say "a EC key" instead of "an EC key", but ah well. (They do say "an RSA key".) May as well match. Update-Note: Code search finds no references to the BoringSSL name, so this is not expected to impact anything. Change-Id: I7563645fd269e4a62fbc46de2647f06bde00e1e4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81428 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Lily Chen <chlily@google.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: 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: