| commit | cfcb0060e8b8fba92d275fa4ac27d369890ea9bf | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Tue Jun 25 10:03:07 2019 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jun 25 18:48:43 2019 +0000 |
| tree | ed6a7599916f2e378d34108a614d672d2f31d0c5 | |
| parent | 7198a233689e250eb36d3d8e96b48b4cafb1be0a [diff] |
Emit empty signerInfos in PKCS#7 bundles. This is our bug that we've had since the beginning of PKCS#7 writing support in eeb9f491: the empty signerInfos SET wasn't emitted. Some parsers, including OpenSSL, don't like this but it appears to have taken five years for anyone to notice. This change does not make parsing strict so that we continue to parse old messages that we may have produced. (As ever, PKCS#* should not be used expect where absolutely required for interoperability.) Bug: b:135982177 Change-Id: Ia7241de69f105657bdfb5ff75e909deae71748a0 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/36564 Commit-Queue: David Benjamin <davidben@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.
There are other files in this directory which might be helpful: