| commit | ae3684469b0499b4c7771218af4dac3092f4b34a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Oct 06 22:49:23 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 07 07:54:52 2025 -0700 |
| tree | 30e44467423063abcf5277b2fc159f709c33406b | |
| parent | 1ae74684a023cccf8d9e6d478e6ea25cd37f7eac [diff] |
Add OIDs and NIDs for ML-DSA-{44,65,87} and ML-KEM-{768,1024}
Match OpenSSL's naming for them, which has more underscores. There's one
use (in Chromium of NID_MLKEM1024), so keep that constant around
briefly, but we should be remove it quickly.
I've matched OpenSSL in how they spell the OIDs in objects.txt, setting
up a !Alias for NIST's sigalg arc. OpenSSL kept the old !Alias around,
but they don't appear in source anywhere, so I'm not sure why. I cleaned
that up.
Since we don't currently plan to implement ML-KEM-512, I skipped that
one. We can always add that later.
Bug: 449751916
Change-Id: I1a5917704db3137785006bdebc34603b0d1ba04b
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82631
Reviewed-by: Lily Chen <chlily@google.com>
Auto-Submit: David Benjamin <davidben@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: