commit | c25c3760ed8c47b9175863f503b2a6ef5b6c61a7 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Wed Aug 28 23:34:36 2024 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 29 16:27:00 2024 +0000 |
tree | d3309b8b75562ccef52c6ebf7dbc154fda5b65b0 | |
parent | 13ef6eaba79be9f018ff1d978bd266cfa44d5fac [diff] |
Add an optional Bazel package to CI Also condition all the tools the Bazel builders won't need. (Perl and Go aren't build dependencies anymore.) Given we've broken this build a couple times, it's clear we need to just put it on CI. This will be paired with a new recipe in the recipes repo. Bug: 42290610 Change-Id: I90a4b376849dee9dde3dfcd12c8df60db1b0120c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70747 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: