| commit | 059585c8dadc7c8170c788f8c89843ee1c5b8f11 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <[email protected]> | Mon Nov 25 15:02:18 2024 -0500 |
| committer | Boringssl LUCI CQ <[email protected]> | Thu Nov 28 00:01:55 2024 +0000 |
| tree | b811d3c5d8ed33843902bb260abc537dcc99d34b | |
| parent | fcef13a49852397a0d39c00be8d7bc2ba1ab6fb9 [diff] |
Update tools and add a .bazelversion So that MODULE.bazel.lock is actually checked to be up-to-date, we should run with --lockfile_mode=error on CI. But since the lock file format changes by Bazel version, that means we also need to pick a particular Bazel version. This matches the best practices documented here: https://bazel.build/external/lockfile#best-practices To update libc++, we now need to pull in a bit of LLVM libc. See https://discourse.llvm.org/t/rfc-project-hand-in-hand-llvm-libc-libc-code-sharing/77701 Change-Id: I53b28067bab86d34be8c76625d6bedc23f0baeba Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/73487 Commit-Queue: Adam Langley <[email protected]> Auto-Submit: David Benjamin <[email protected]> Reviewed-by: Adam Langley <[email protected]>
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: