| commit | 251ee0b761b165ce815c760065dba4b5721e8d06 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Nov 29 13:31:13 2023 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 29 21:55:48 2023 +0000 |
| tree | 8b55c4b1e96f40f383a1d21e1881377ace97f0fc | |
| parent | 2ba7634b9e2b33875e2a40dec9e04abffe061f2c [diff] |
Implement the old FIPS 186-2 PRF FIPS 186-2 included some ad-hoc PRF, based on SHA-1's internals, to generate some numbers for DSA, though nothing uses it for DSA anymore. However, it made its way into EAP-SIM and EAP-AKA. Some applications implement it by reaching into the SHA_CTX structure. https://boringssl-review.googlesource.com/c/boringssl/+/63967 broke some of those callers. Rather than revert it, just add a support API for this PRF and we'll move that caller to it. Reference: https://csrc.nist.gov/files/pubs/fips/186-2/upd1/final/docs/fips186-2-change1.pdf Bug: 566, 667 Change-Id: I5821811f15f20f9f43165fcda23befad03ff277a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/64307 Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Bob Beck <bbe@google.com> Auto-Submit: 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: