| commit | 40ec347196a939bd4fd1f801df896b2f4e2205dc | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Sep 10 18:36:58 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 11 00:38:27 2024 +0000 |
| tree | e47c2193e2d0df40d5c63eeacbd95a62495da781 | |
| parent | 6abe18402eb2a5e9b00158c6459646a948c53060 [diff] |
Switch to rules_license Apparently Bazel has deprecated the built-in licenses() command and now expects you to pull in an external package. I think I've gotten this right? Since our new BUILD.bazel file is actually referenced by the old -with-bazel branch, this new dependency also needs to work there. That is still using the legacy WORKSPACE system, but I got that working there too, I think. However, as the legacy WORKSPACE system does not consider recursive dependencies, anyone using it and updating BoringSSL will need to, in turn, update their WORKSPACE file on update. Fixed: 365824757 Change-Id: I7b49f33d628cec2ec07a47f0e31f16765d0f532a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71147 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Ben Lawson <benlawson@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: