| commit | 8b8d22c961413c1ae465719d8252bea50587ed3f | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Jan 01 05:13:22 2017 -0500 |
| committer | Adam Langley <agl@google.com> | Thu Jan 12 16:56:05 2017 +0000 |
| tree | 06411b3e0f31512e91c428b7fa4e20b3b2088fbb | |
| parent | 2df010e4f4eae6806cd1d855b63c3891116f065d [diff] |
Parse PKCS#12 files more accurately. Mercifully, PKCS#12 does not actually make ContentInfo and SafeBag mutually recursive. The top-level object in a PKCS#12 is a SEQUENCE of data or encrypted data ContentInfos. Their payloads are a SEQUENCE of SafeBags (aka SafeContents). SafeBag is a similar structure to ContentInfo but not identical (it has attributes in it which we ignore) and actually carries the objects. There is only recursion if the SafeContents bag type is used, which we do not process. This means we don't need to manage recursion depth. This also no longer allows trailing data after the SEQUENCE and removes the comment about NSS. The test file still passes, so I'm guessing something else was going on? Change-Id: I68e2f8a5cc4b339597429d15dc3588bd39267e0a Reviewed-on: https://boringssl-review.googlesource.com/13071 Reviewed-by: 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.
There are other files in this directory which might be helpful: