Reland "crypto: Detect ARMv8.4-a DIT support" This is a reland of commit 5fa9e920fe867353a5a0a6eee4005e20aa3df85d with a change in the way we encode the DIT register in reading and writing the PSTATE flag. We ran into issues with toolchains that do not understand the DIT alias and we now use a direct encoding. Original change's description: > crypto: Detect ARMv8.4-a DIT support > > Bug: 368256344 > Change-Id: I3ddaef793aaf816c164f288c1ef4e8946a6a6964 > Signed-off-by: Xiangfei Ding <xfding@google.com> > Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/103067 > Reviewed-by: David Benjamin <davidben@google.com> Bug: 368256344 Change-Id: I33d44f741bf6de513d3f7e338fcc153760273025 Signed-off-by: Xiangfei Ding <xfding@google.com> Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/105809 Reviewed-by: 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: