commit | a61e7475d3145836cc11469f328ad7c98e7cf527 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Fri Sep 23 15:04:20 2022 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 23 19:32:20 2022 +0000 |
tree | 2c7c089e96238a1720d5b65bbbdef9756d7c9f17 | |
parent | 04989786e9ab16cef5261bbd05a2b1a8cb312dbf [diff] |
Also check for V_ASN1_NEG_INTEGER when checking types. ASN1_STRING's representation is confusing. For specifically INTEGER and ENUMERATED, it lifts the sign bit into the type. While negative serial numbers aren't actually valid, we do accept them and test code sometimes uses these APIs to construct them, so amend https://boringssl-review.googlesource.com/c/boringssl/+/54286 to allow them. I've also switched the CRL one to an assert. On reflection, returning 0 for a CRL lookup is failing closed, so it seems better to just continue to accept the ASN1_STRING, even if it's the wrong type. Change-Id: I1e81a89700ef14407a78bd3798cdae28a80640cd Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54525 Reviewed-by: Adam Langley <agl@google.com> Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: 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.
Project links:
There are other files in this directory which might be helpful: