commit | 4a264b2c1fce97f5b99478cc1a002e016d0b7bb0 | [log] [tgz] |
---|---|---|
author | Adam Langley <agl@google.com> | Thu Jan 26 18:02:20 2023 +0000 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 26 18:20:05 2023 +0000 |
tree | b73e4841b9dad7fc8f3ed1a2f465087b20477f66 | |
parent | 1e97ce3beab9e6d34bc645f6901b2b30b50530c0 [diff] |
Also remove poly_rq_mul.S from generate_build_files.py 97873cd1a5 removed the HRSS assembly, but that file was special-cased in generate_build_files.py and so an update is also needed there. Change-Id: I3c99989da5faee6b39a3b90fee5fa89c20997c64 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/56345 Auto-Submit: Adam Langley <agl@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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: