| commit | 5ecb88b95b7930c7b83f26a76ed13aeeb71de88a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Oct 04 17:51:35 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Oct 05 14:34:58 2016 +0000 |
| tree | 6d06027252a5ba20b15a10824461cc8cb8e5caf6 | |
| parent | 3871dc9e39eea02d669f5d517c0d3c74155eca52 [diff] |
Make EnableAllCiphers client-only and rename. EnableAllCiphers is problematic since some (version, cipher) combinations aren't even defined and crash. Instead, use the SendCipherSuite bug to mask the true cipher (which is becomes arbitrary) for failure tests. The shim should fail long before we get further. This lets us remove a number of weird checks in the TLS 1.3 code. This also fixes the UnknownCipher tests which weren't actually testing anything. EnableAllCiphers is now AdvertiseAllConfiguredCiphers and does not filter out garbage values. Change-Id: I7102fa893146bb0d096739e768c5a7aa339e51a8 Reviewed-on: https://boringssl-review.googlesource.com/11481 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: