| commit | ba80c5ef1af7d79c265db0e8f9b672b23b6e85ef | [log] [tgz] |
|---|---|---|
| author | Daniel McCarney <daniel@binaryparadox.net> | Tue Feb 04 14:27:50 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 07 09:34:03 2025 -0800 |
| tree | 0503e1a4c8617b659932a55b5625c03fa4cf61cd | |
| parent | 91eb0750a344113f88d4d24139acfa6d9267f579 [diff] |
util/fipstools: generalize hkdf KDA subprocess Previously the only KDA ACVP algorithm mode supported by the acvptool was HKDF mode, and so the file was called hkdf.go and didn't interrogate the vector set mode. In preparation for supporting the OneStepNoCounter KDA mode we need to generalize the subprocess handler as both it and HKDF KDA are advertised as "KDA" algorithms and must be multiplexed on the "mode". To simplify review this commit moves the existing HKDF code, and adds the small bit of multi-plexing required to dispatch by mode, but doesn't introduce any other changes. Change-Id: I3ad640d6b3fa93483c8fac6cadcfb88cf9da5430 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/75927 Reviewed-by: Adam Langley <agl@google.com> Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: Bob Beck <bbe@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: