commit | f6cf8bbc84b4f6c82b784a229ba360afbaea6332 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Fri Feb 02 19:12:10 2018 -0500 |
committer | Adam Langley <agl@google.com> | Sun Feb 11 01:03:17 2018 +0000 |
tree | 4298171d06fe31615126b9f52af46a2fd349ae32 | |
parent | 6dc994265edb2967462e88b2678035a870a2233f [diff] |
Sync up AES assembly. This syncs up with OpenSSL master as of 50ea9d2b3521467a11559be41dcf05ee05feabd6. The non-license non-spelling changes are CFI bits, which were added in upstream in b84460ad3a3e4fcb22efaa0a8365b826f4264ecf. Change-Id: I42280985f834d5b9133eacafc8ff9dbd2f0ea59a Reviewed-on: https://boringssl-review.googlesource.com/25704 Reviewed-by: Adam Langley <agl@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.
There are other files in this directory which might be helpful: