| commit | d15c01960f7623c8df0b20c08dc59e1a65adbf08 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Jan 08 13:46:55 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 03 14:48:57 2025 -0800 |
| tree | 76ca61b5a2dde121716f26786c78b80f0c8a3a11 | |
| parent | 40c2135026816840bd17477249c91d8e4e51afd6 [diff] |
Remove other references to additional licenses These files, with any subsequent upstream modifications, were taken from OpenSSL under OpenSSL's licensing, so use that one to avoid ambiguity. See also these OpenSSL changes: https://github.com/openssl/openssl/commit/389c09fa0932f260b2cb17b8b57d9835326e10c6 https://github.com/openssl/openssl/commit/c879f8ac56170a5cf929fab8067beb2a5902be2b Bug: 364634028 Change-Id: Id4667d998a142698dfd7b2523a67340318326abe Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/75849 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: 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: