| commit | e09c171f24d555f17bca2c87d2bf63b5565eed4c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Dec 29 18:55:38 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 03 19:02:29 2025 -0800 |
| tree | 284f611f2f1e51f86bf40d54b967f2afaafcd368 | |
| parent | 6a12f1734a30385faacada4283bcdfb0e72d4794 [diff] |
Import upstream changes to copyright lines This imports the following changes from OpenSSL: * https://github.com/openssl/openssl/commit/aa8f3d76fcf1502586435631be16faa1bef3cdf7 * https://github.com/openssl/openssl/commit/5aba2b6e88d1d7fc921d2161af27a0835f966ea9 * https://github.com/openssl/openssl/commit/c80149d9f09b3a5a5b1621fa705e900d455334d4 See the following links for some related discussion in OpenSSL's repository: * https://github.com/openssl/openssl/pull/3663 * https://github.com/openssl/openssl/pull/3684 * https://github.com/openssl/openssl/pull/3585#issuecomment-309793470 * https://github.com/openssl/openssl/pull/3685 The copyright_summary script may be used to compare this CL. Note there is one change to ecdsa_test.cc to align with OpenSSL. See go/openssl-copyright-consolidation-comparison (internal-only). Bug: 364634028 Change-Id: I987c4e145d2ccd0c32bbf9e7bb2cc69e89019d35 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/74712 Reviewed-by: Adam Langley <agl@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: