commit | 7c1f40f2f8fd04f4595be47b3a676d6587dd2943 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Sat Oct 16 01:42:41 2021 -0400 |
committer | Adam Langley <agl@google.com> | Mon Oct 18 16:16:33 2021 +0000 |
tree | 0f02368c5c8b361dff0118a1aa80fb987bb6a8a7 | |
parent | bb88f52261f3231005c7fa43e55cc888d2f9f582 [diff] |
Reword ASN1_BOOLEAN exception. There are potentially more than three ASN1_BOOLEAN ASN1_ITEMs. ASN1_BOOLEAN may be wrapped by explicit or implicit tagging into another ASN1_ITEM. (I also suspect SEQUENCE OF BOOLEAN is just unrepresentable in this library, but I will leave that rabbithole alone.) Bug: 426 Change-Id: I3e58bfb63ee5c7a6d112b4a16e0f13fbacaea93a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/49925 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.
Project links:
There are other files in this directory which might be helpful: