| commit | 4b0d0e4c5ef19055b3ff17ed3d760f9b10d76641 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Oct 28 17:17:14 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Oct 28 21:25:35 2016 +0000 |
| tree | 7cff3c54a064f3d98d5bf4589f4d404fc9571525 | |
| parent | ea213d1f0b655d60793b67337bac2019c37300e7 [diff] |
Validate input iv/mac sizes in SSL_AEAD_CTX_new. This should never happen, but the SSL_AEAD_CTX_new layer should enforce key sizes as it's not locally obvious at the call site the caller didn't get confused. There's still a mess of asserts below, but those should be fixed by cutting the SSL_CIPHER/SSL_AEAD_CTX boundary differently. (enc_key_len is validated by virtue of being passed into EVP_AEAD.) BUG=chromium:659593 Change-Id: I8c91609bcef14ca1509c87aab981bbad6556975f Reviewed-on: https://boringssl-review.googlesource.com/11940 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@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: