| commit | b0651775c215728b0276860a4590a873cff6e4ca | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Jul 10 16:39:36 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jul 10 23:54:41 2017 +0000 |
| tree | 1ba949c0378a2bf57f36858e2b93f20ed238756a | |
| parent | 08fea48a91654c57d78563a7623f3b0e4f825610 [diff] |
Reduce the alignment tag on aead_aes_gcm_siv_asm_ctx. This tag doesn't actually do anything, except cause UBSan to point out that malloc doesn't align that tightly. malloc does, however, appear to align up to 16-bytes, which is the actual alignment requirement of that code. So just replace 64 with 16. When we're juggling less things, it'd be nice to see what toolchain support for the various aligned allocators looks like. Or maybe someday we can use C++ new which one hopes is smart enough to deal with all this. Change-Id: Idbdde66852d5dad25a044d4c68ffa3b3f213025a Reviewed-on: https://boringssl-review.googlesource.com/17706 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: 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: