commit | abb32cc00dd4086f7b2213a5d3ecd223be937831 | [log] [tgz] |
---|---|---|
author | Adam Langley <alangley@gmail.com> | Thu Jan 12 16:15:20 2017 -0800 |
committer | Adam Langley <alangley@gmail.com> | Mon Jan 16 16:53:32 2017 +0000 |
tree | a6a984713613a8b6bef36377c268d7d9c4934007 | |
parent | 67ccf59161156071cd16be2fb3dff5911b95b869 [diff] |
Restore H (the key) in the GHASH context. This was removed in a00cafc50ca599cc91f240f5347f0a01cca7bf7d because none of the assembly actually appeared to need it. However, we found the assembly the uses it: the MOVBE-based, x86-64 code. Needing H seems silly since Htable is there, but rather than mess with the assembly, it's easier to put H back in the structure—now with a better comment. Change-Id: Ie038cc4482387264d5e0821664fb41f575826d6f Reviewed-on: https://boringssl-review.googlesource.com/13122 Reviewed-by: Adam Langley <alangley@gmail.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: