| tag | 1e10fd0c3312344560576243c4ce592e019a9d00 | |
|---|---|---|
| tagger | David Benjamin <davidben@google.com> | Fri Sep 13 16:03:46 2024 -0700 |
| object | 58f3bc83230d2958bb9710bc910972c4f5d382dc |
0.20240913.0
| commit | 58f3bc83230d2958bb9710bc910972c4f5d382dc | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Sep 13 18:53:38 2024 -0400 |
| committer | David Benjamin <davidben@google.com> | Fri Sep 13 22:58:25 2024 +0000 |
| tree | 8a76559bdaa07ae6179ecd469daec97b3f36cab6 | |
| parent | 581f83dcdbbbe827ca8eda20b85ec869b8be1e99 [diff] |
Add templates for Publish to BCR Not sure if these are correct. I added a README so that our future selves have some hope of figuring out what this is for. The metadata and presubmit files I copied from our existing BCR entries. https://github.com/bazelbuild/bazel-central-registry/blob/main/modules/boringssl/0.0.0-20240530-2db0eb3/presubmit.yml https://github.com/bazelbuild/bazel-central-registry/blob/main/modules/boringssl/metadata.json Change-Id: Ice8b7dee7360e44f77411db6fec8067a3204aa0b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71287 Commit-Queue: David Benjamin <davidben@google.com> Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: 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: