| commit | de186e49bf6492e982fd2b910c75880209528dcd | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jul 25 05:41:44 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 25 08:09:20 2025 -0700 |
| tree | cfb21a6d1120f103d642abbf4c73521e207184a2 | |
| parent | a873ab7906bc5b1431821864df8036068aab972d [diff] |
Work around a Rust problem tripped by working around a Rust problem, which in turn was tripped by working around a Rust problem We are now several layers deep in working around problems in this language. Rust's bindgen cannot even bind headers that reference <stdio.h> without tripping a Rust warning due to https://github.com/rust-lang/rust-bindgen/issues/2807 As a result we need to manually suppress the warning. However, that warning is not available until newer Rusts, so trying to suppress the warning causes a different warning in older Rusts. https://boringssl-review.googlesource.com/c/boringssl/+/80707 attempted to work around this Rust bug by using cfg_version, but that broke the Chromium build because it is not part of Stable Rust. Stable Rust has not yet caught up to C89 in having some way to condition code on version. Instead, suppress the future lint by just suppresing unknown lints. Also add some comments so we remember where all this nonsense came from. This unbreaks the Chromium roll. Change-Id: I47dcedadae5695b2edab05dfbc08a9cd8cfafdc1 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/80747 Commit-Queue: Adam Langley <agl@google.com> Auto-Submit: David Benjamin <davidben@google.com> 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:
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: