| commit | 8ef8f5838a8adbbeb7bea8cab24acce8583795e4 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@chromium.org> | Tue Jun 17 14:06:01 2025 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 13 11:36:32 2025 -0700 |
| tree | 1b583f7caa829f2a30c67aee99346c5946e69d61 | |
| parent | 5481e363e80df23b909d477b60ff036ad26fc5df [diff] |
Switch to using a derivation function in CTR-DRBG. Upcoming NIST rule changes are expected to effectively require us to pass in larger entropy inputs to the DRBG, which requires us to use the "derivation function" option from 800-90A. This change implements the derivation function and splits the entropy and nonce arguments out, as needed for this style of DRBG. Since we have external users of the existing CTR-DRBG mode, that is still supported, but all internal uses will now use a derivation function. Change-Id: I8079e9f4c6238e91c68fef1e40189211f4142555 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79768 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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: