commit | 05750f23aec26bd80fe6a8fbdfab47efadda7212 | [log] [tgz] |
---|---|---|
author | Adam Langley <agl@google.com> | Mon May 14 14:28:36 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon May 14 22:09:29 2018 +0000 |
tree | b2b584e8e3006d1353d1746bd8988ae49a47ce52 | |
parent | 5b220ee70df2de898ec55e79a6824e85479fe1c5 [diff] |
Revert "Revert "Revert "Revert "Make x86(-64) use the same aes_hw_* infrastructure as POWER and the ARMs."""" This was reverted a second time because it ended up always setting the final argument to CRYPTO_gcm128_init to zero, which disabled some acceleration of GCM on ≥Haswell. With this update, that argument will be set to 1 if |aes_hw_*| functions are being used. Probably this will need to be reverted too for some reason. I'm hoping to fill the entire git short description with “Revert”. Change-Id: Ib4a06f937d35d95affdc0b63f29f01c4a8c47d03 Reviewed-on: https://boringssl-review.googlesource.com/28484 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: