| commit | 35fb591f242ec6b34ed24eb1c2cb7adb13fcf3b7 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Tue Oct 16 12:11:51 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Oct 22 23:12:57 2018 +0000 |
| tree | 1ad0fa81acbc81d72a178287fc7dfb0abaa80edc | |
| parent | c0c9001440db8121bdc1ff1307b3a9aedf26fcd8 [diff] |
Flatten EVP_AEAD_CTX An EVP_AEAD_CTX used to be a small struct that contained a pointer to an AEAD-specific context. That involved heap allocating the AEAD-specific context, which was a problem for users who wanted to setup and discard these objects quickly. Instead this change makes EVP_AEAD_CTX large enough to contain the AEAD-specific context inside itself. The dominant AEAD is AES-GCM, and that's also the largest. So, in practice, this shouldn't waste too much memory. Change-Id: I795cb37afae9df1424f882adaf514a222e040c80 Reviewed-on: https://boringssl-review.googlesource.com/c/32506 Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 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: