| commit | 864a235afcf4d2575b1eab8de96fbf0d84f6cda9 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun May 04 14:09:42 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 07 10:46:04 2025 -0700 |
| tree | 359cd3447f1a3845b5d1ba9855a58aaa8a9f3412 | |
| parent | 95f79606901e64c1d494a4b786350e2287cf8fa7 [diff] |
Don't stack-allocate incomplete X509/X509_CRL objects As we start putting more types with destructors into our types, we won't be able to just stack-allocate them and ignore object lifetimes. In particular, using a proper std::atomic<uint32_t> as the refcount is incompatible this pattern. This particular file needs loads more work, but I've just done the minimal change needed here. Change-Id: If55244303e5b2ff7212ad4eba0c184a2ce1a15c0 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79067 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> Auto-Submit: 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: