| commit | 305e5c570be4b142e8590d37dd9136b60f12b9bc | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Jan 07 01:52:59 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 14 09:02:17 2025 -0800 |
| tree | 952d81fe3fdbc77b7aa78a4c51f4e39e6bfcd80e | |
| parent | 06410babf542327d0b80b3a23e0dd51a8b3fd57c [diff] |
Unfork Chromium's Clang update script We can DEPS in individual directories and just run the actual script. This avoids needing to maintain our own copy, and also means we can potentially use Chromium's Rust build later. (The Rust update script pulls in the Clang one.) We should also be able to unfork vs_toolchain.py, but there's a minor headache around it ending up in the LUCI copy of depot_tools and not being cached. Avoiding that seems to require enough fuss that it might be easier to switch to the windows_sdk recipe module, even if that VS toolchain isn't updated as frequently. Change-Id: Icc4ca117d0187b616747711cb563f766cd3f9aba Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/74889 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:
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: