| commit | 06296a8d063967d452a34d06320236cc68bef7ed | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Aug 27 14:49:25 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 03 20:52:57 2025 -0700 |
| tree | f80f2ca34a7a71608a5f4119d2e0ac4bc50803c3 | |
| parent | 26111abe5ba1546ed41a8940a609c58445b853c0 [diff] |
Make CBS/CBB-versions of crypto/asn1 types I had hoped to do this incrementally, but X509_ALGOR contains an ASN1_TYPE, so all types get imported at once. For now, these functions are just wired up to tasn_dec.cc, but subsequent changes will read them one-by-one. For the parse convention, I opted for a caller-supplied output variable, even though we've generally tried to avoid object reuse in the caller-exposed d2i functions. At the level of core ASN.1 types, the object reuse is hopefully manageable (and in practice I expect they'll always be in the empty state). The motivation here is to let us internally embed types into the X509, etc., structs and avoid the layers of tiny allocations. This does mean that the dispatch code inside ASN1_TYPE and the dispatch code in tasn_dec.cc is no longer shared, but that sharing wasn't valid by strict aliasing anyway. (Nothing in tasn_dec.cc is valid by strict aliasing.) Bug: 42290417 Change-Id: Idb6910e23f4fa4d01ee39ebcbf2ae09df14e87e3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81772 Reviewed-by: Adam Langley <agl@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: