| commit | d2ed382e647bfe6148bdc192d77b48406af85a94 | [log] [tgz] |
|---|---|---|
| author | Matthew Braithwaite <mab@google.com> | Tue Jul 10 16:27:22 2018 -0700 |
| committer | Matt Braithwaite <mab@google.com> | Fri Nov 02 19:45:42 2018 +0000 |
| tree | d0b6e0aafa203bb7a50b38e4caed131450cba3c1 | |
| parent | e62bf02a131a14b6ec6ebea3590342a6c8265bbf [diff] |
Serialize SSL configuration in handoff and check it on application. A split SSL handshake may involve 2 binaries, potentially built at different versions: call them the "handoff/handback" binary and the "handshake" binary. We would like to guarantee that the handoff/handback binary does not make any promises that the handshake binary cannot keep. As a start, this commit serializes |kCiphers| to the handoff message. When the handoff message is applied to an |SSL|, any configured ciphers not listed in the handoff message will be removed, in order to prevent them from being negotiated. Subsequent commits will apply the same approach to other lists of features. Change-Id: Idf6dbeadb750c076ab0509c09b9d3f22eb162b9c Reviewed-on: https://boringssl-review.googlesource.com/c/29264 Reviewed-by: Matt Braithwaite <mab@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: