| commit | a00cafc50ca599cc91f240f5347f0a01cca7bf7d | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Wed Nov 30 12:37:45 2016 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Dec 02 20:59:47 2016 +0000 |
| tree | 0345beaed86c20ebb1b66b99e85ea11ef3eaf296 | |
| parent | e8bbc6cf6cf6fbff65e461d8e670f2ed8c18d206 [diff] |
Drop H (the key) from the GCM context. The key is only needed during initialisation because after that point it is implicit in the table of powers. So no need to keep it around. There was a non-specific “haunted house” comment about not changing this, but I've successfully tested with all the assembly versions so I think that comment is no longer true. Change-Id: Id110156afb528904f114d9a4ff2440e03a1a69b8 Reviewed-on: https://boringssl-review.googlesource.com/12477 CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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.
There are other files in this directory which might be helpful: