commit | 09050cb498336655883157c6e6055db9e5542857 | [log] [tgz] |
---|---|---|
author | Adam Langley <agl@google.com> | Wed Jul 10 11:12:24 2019 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jul 10 21:14:32 2019 +0000 |
tree | faa5b34dc3d9f36f5e33a5eef3cb38f0e178ff0c | |
parent | 365b7a0fcbf273b1fa704d151059e419abd6cfb8 [diff] |
Add SipHash-2-4. The added code is a one-shot function. A handful of instructions could be saved by having a context object for repeated use of the same key, but perhaps it's not needed. Selected the 2-4 variant to implement because it seems to be overwhelmingly the most commonly used. Change-Id: I1e4f699f7dd5a2d35e12245fa116bafbd3439979 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/36664 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: 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: