| commit | 898de8d09e10960e64901e2d9836cdea5dd1d1a6 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Mar 11 12:26:37 2023 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 16 23:46:11 2023 +0000 |
| tree | 552369ae1ba66c785b3c5d253ef11e7324d978fa | |
| parent | 173b63942dd0c58a67a354dbb4b86c6f752aac6a [diff] |
Rewrite c2i_ASN1_OBJECT Removing object reuse makes it dramatically simpler. Along the way, lift the OID validity checker into crypto/bytestring, so we can use it more generally. (Although the difference between invalid OID and unknown OID is pretty academic, so this check isn't that important.) For now I've preserved the existing behavior, where the OID validity checker accepts arbitrarily large OID components. Though this results in an oddity where the OID to string functions reject inputs that the parser accepts. (There we only allow up to 2^64-1.) Update-Note: When we removed object-reuse from all the d2i functions, we missed one d2i_ASN1_OBJECT. See https://boringssl-review.googlesource.com/c/boringssl/+/56647. Otherwise, this CL is not expected to change behavior. Change-Id: If4d2d83d9f3c96abfdc268e156f2cf3a9a903b0c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/58147 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: