| commit | 5d9ffb810b2c5c7aaa6700161989d19547983b5f | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Aug 07 18:01:11 2023 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 08 17:03:47 2023 +0000 |
| tree | 354abb68e3f16e41a0c3d8abd159ae15357d8ec1 | |
| parent | 822d63cb07c7d7f435bd6893193eb05153a58b3d [diff] |
Remove the remaining old-style asm lists I think there are a couple projects remaining that still use the old lists here, but they're in repositories we don't spend as much time in, and it should be straightforward for them to update when they get here. Removing these should put us in a good place to check in pre-generated asm lists. While I'm here, fix a few typos in TODOs I previously added. Update-Note: If you're one of those projects and have trouble switching to the new lists, let us know. Bug: 542 Change-Id: I57559bafc85eceacc7a237e2f29db6eaf492a8cb Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/62186 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:
There are other files in this directory which might be helpful: