| commit | 0ee584bb5134f8e6b5d2e90f5dc9334ae460a507 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@chromium.org> | Wed Aug 21 12:14:10 2024 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 21 19:54:38 2024 +0000 |
| tree | 509dc94b913494277e607e699b617fb946945ed2 | |
| parent | 526a3c49a2f04c3b55a909b80b98b2d56e80aefc [diff] |
ML-DSA: focus the API on saving private keys as seeds. There are two ways to save an ML-DSA or ML-KEM private key: NIST specifies a partial serialization of the contents of the keys and this takes up several kilobytes. But one can also save the seed that the key was generated from and simply regenerate the private key as needed. * The seed is approximately two orders of magnitude smaller. * It is fast to expand a private key from a seed. * The NIST format requires validating several aspects of the partially expanded private key. Because of this, seeds seem clearly better and having two different serializations in the API is a bit weird when currently neither of them are used anywhere. Thus this change emphasizes using seeds to save private keys and moves the marshalling function for the NIST format into the internal API. ML-KEM already follows this pattern, although saving the seed is still optional there because ephemeral keys are a major use case for ML-KEM. Change-Id: I439224e745ad8747d26f57288f1d503593e0e52c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70407 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: 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:
There are other files in this directory which might be helpful: