commit | 1f786137e4045b88d26035306ef826ff4a30befd | [log] [tgz] |
---|---|---|
author | Anne Redulla <aredulla@google.com> | Wed Jul 12 13:53:30 2023 +1000 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 14 15:21:20 2023 +0000 |
tree | 54f79ef4be68699a42240ed9d6b5358c69822414 | |
parent | 26ecb2a275ca7444d10899b8a3fe76d84831fca4 [diff] |
[ssci] Added Shipped field to READMEs This CL adds the Shipped field (and may update the License File field) in Chromium READMEs. Changes were automatically created, so if you disagree with any of them (e.g. a package is used only for testing purposes and is not shipped), comment the suggested change and why. See the LSC doc at go/lsc-chrome-metadata. Bug: b:285450740 Change-Id: I63755d8a42ea69ff6d3a4e0c21ddacd2b7ce9053 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/61545 Auto-Submit: Anne Redulla <aredulla@google.com> Reviewed-by: David Benjamin <davidben@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:
There are other files in this directory which might be helpful: