|author||David Benjamin <firstname.lastname@example.org>||Mon Feb 25 15:46:56 2019 -0600|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Mar 04 20:23:09 2019 +0000|
Check in vpaes-armv8.pl from OpenSSL unused and unmodified. This is done separately to make the diffs in the subsequent CL easier to see. Imported from OpenSSL at revision 25ca718150cef41e1c1d9c2c8c58e2b1e2cad3fa. Bug: 246 Change-Id: I9e7067ea177963fb9b77bf6fb39702ffe6e34ed4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35025 Commit-Queue: David Benjamin <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org>
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.
There are other files in this directory which might be helpful: