| commit | 89d18c7a880fe43a5cebe39837178c9e6161c3cb | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Jan 25 14:53:57 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 25 20:13:24 2024 +0000 |
| tree | f4dce773fb79bef52473bfb8e3be372ec9e338ef | |
| parent | 77ee4e4609cfb3480e1a554790348ebcab61313e [diff] |
Import upstream tests for CVE-2024-0727 BoringSSL is not affected by CVE-2024-0727, but these are good cases to have in our unit tests. PKCS#12 is built on top of PKCS#7, a misdesigned, overgeneralized combinator format. One of the features of PKCS#7 is that the content of every ContentInfo may be omitted, to indicate that the value is "supplied by other means". This is commonly used for "detached signatures", where the signature is supplied separately. This does not make sense in the context of PKCS#12. But because PKCS#7 combined many unrelated use cases into the same format, so PKCS#12 (and any other use of PKCS#7) must account for and reject inputs. Change-Id: I22f19b6c14894003f7515206cd34f968e5503d4a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65747 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@google.com> Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: 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:
There are other files in this directory which might be helpful: