| commit | 09ae7fe069acea750fba7065e43b3fa5ff180ce0 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Oct 08 13:40:42 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 08 16:38:48 2025 -0700 |
| tree | 616446e03bed1ad5c90a4a3d92642134bd3cab90 | |
| parent | 87dff582e4f49bacdd6526f807d2a7cd52b17831 [diff] |
Don't have separate BCM and ML-KEM and ML-DSA types This avoids a ton of casts, means the BCM and public APIs can interoperate a bit more straightforwardly, and changing the types no longer needs to update two copies of the struct. Even when we were pursuing a crisper BCM and libcrypto split, this division wouldn't have done anything useful because we would be forever forced to keep them exactly the same size. While I'm here, remove a bunch of unnecessary `struct`s. In C++, they are not needed. We can't avoid them in the public headers. (Public headers should probably follow the OpenSSL struct + typedef convention to avoid this.) Bug: 450044889 Change-Id: I9d9cde41de1df380c0f928c559433eff6b97666a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82688 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@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: