| commit | 8803c0589dbb565fed74c70a556212f1eb16d132 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Jun 21 14:26:17 2018 -0400 |
| committer | Adam Langley <agl@google.com> | Tue Jun 26 07:23:10 2018 +0000 |
| tree | 6c7e9256d431d624a685538d65403a83bbf6cbd9 | |
| parent | b4810de60f151e9848b19a87d9679f3befcd39b2 [diff] |
Properly advance the CBS when parsing BER structures. CBS_asn1_ber_to_der was a little cumbersome to use. While it, in theory, allowed callers to consistently advance past the element, no caller actually did so consistently. Instead they would advance if conversion happened, and not if it was already DER. For the PKCS7_* functions, this was even caller-exposed. Change-Id: I658d265df899bace9ba6616cb465f19c9e6c3534 Reviewed-on: https://boringssl-review.googlesource.com/29304 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: