| commit | b402cff383c5d150bc69d9c5c0d9288d718caf5b | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Aug 17 20:05:19 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 28 09:55:01 2025 -0700 |
| tree | badd3e78c873b17d952d52952b4d48ddc4bd309f | |
| parent | 136d6b7f6139e0f7ba1ca6418cce26e552e0fce8 [diff] |
Add internal EC parsing functions that take lists of allowed groups They're internal for now; I'm thinking we'll just have the public versions of these at the EVP layer for now and try to move past this mess where there's two versions of every API. The API is mildly annoying in that both this caller and the one added next will want to distinguish UNKNOWN_GROUP from other errors, but the recent helper function makes checking the error queue not tooooo bad. Bug: 42290364 Change-Id: Ibb5e3e643a9180459cc09b4559ee40696cea2688 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81650 Reviewed-by: Adam Langley <agl@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: