| commit | 71666cb87c4de0bbc34df783e571bdc936f38b0b | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue May 01 17:14:27 2018 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue May 01 23:28:59 2018 +0000 |
| tree | 459536eeed0b18e2ca4a088314dbd73e61008647 | |
| parent | b7bc80a9a632ab0c69598382304b14a63e8cae72 [diff] |
Allow renego and config shedding to coexist more smoothly. Chrome needs to support renegotiation at TLS 1.2 + HTTP/1.1, but we're free to shed the handshake configuration at TLS 1.3 or HTTP/2. Rather than making config shedding implicitly disable renegotiation, make the actual shedding dependent on a combination of the two settings. If config shedding is enabled, but so is renegotiation (including whether we are a client, etc.), leave the config around. If the renegotiation setting gets disabled again after the handshake, re-evaluate and shed the config then. Bug: 123 Change-Id: Ie833f413b3f15b8f0ede617991e3fef239d4a323 Reviewed-on: https://boringssl-review.googlesource.com/27904 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 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: