| commit | 6f4159567deb1a3d7b15108556360f97a2b57124 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Dec 10 21:28:37 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Dec 11 13:52:41 2024 -0800 |
| tree | 597e3fc8d33e8f5b80383b30a243cc375d61b9d0 | |
| parent | e43169a421099d99d1f9c78409704a3128cb22e8 [diff] |
Start maintaining an AUTHORS file Following the guidance in https://opensource.google/documentation/reference/releasing/authors, start maintaining an AUTHORS file. Update all existing Google copyright lines to 'The BoringSSL Authors' per the document. This CL also changes the styling to match the new guidance: removed the '(c)' and the comma. All other existing copyright lines are left unmodified. Going forward, our preference will be that new contributions to BoringSSL use 'The BoringSSL Authors', optionally adding to the AUTHORS file if the contributor desires. To avoid being presumptuous, this CL does *not* proactively list every past contributor in the BoringSSL half of the AUTHORS file. Past contributors are welcome to send us a patch to be added, or request that we add you. (Listed or not, the commit log continues to be a more accurate record, and any existing non-Google copyright lines were left unmodified.) The OpenSSL half of the AUTHORS file is seeded with the contents of the current OpenSSL AUTHORS file, as of writing. The current contents in the latest revision of the 1.1.1 branch (b372b1f76450acdfed1e2301a39810146e28b02c) and master (d992e8729ee38b082482dc010e090bb20d1c7bd5) are identical, just formatted in text vs Markdown. Note when reviewing: CONTRIBUTING.md and AUTHORS contain non-mechanical changes. Bug: 364634028 Change-Id: I319d0ee63ec021ad85e248e8e3304b9cf9566681 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/74149 Commit-Queue: David Benjamin <davidben@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: