tag | 6abe848d27006e8b70dd9617bfd2f449f8127ea8 | |
---|---|---|
tagger | David Benjamin <davidben@google.com> | Tue Oct 01 15:51:01 2024 -0700 |
object | 81345b84505e9c23c156b2c7a1e655a204bd3e9a |
0.20240930.0
commit | 81345b84505e9c23c156b2c7a1e655a204bd3e9a | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Mon Sep 30 11:16:33 2024 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 01 22:18:09 2024 +0000 |
tree | 3d0c73357f72068fd090b94121b6394b1e223801 | |
parent | f8bb652b01d3b34a20ddbaaa35def260783ee734 [diff] |
Bump module version and Bazel dependencies Not sure what cadence we'll settle to for these snapshots, but let's kick off another one. I've gone ahead and updated the dependencies from https://registry.bazel.build, because it seemed natural to just do those at the same time. Change-Id: Ifa609a80c110a1cbf196f9f1a23fb8d533b029f9 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71667 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: Bob Beck <bbe@google.com> Auto-Submit: David Benjamin <davidben@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: