| commit | 163c95691a0e6f115d0b51db36325e77fae7f018 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Aug 29 23:14:17 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Aug 30 15:43:35 2016 +0000 |
| tree | 30be9b879a23b4856d73f9072579b8dc66001cff | |
| parent | 147f1c468c937e0d05c9d1168f709c316a0697d2 [diff] |
Forbid EMS from changing during renegotation. Changing parameters on renegotiation makes all our APIs confusing. This one has no reason to change, so lock it down. In particular, our preference to forbid Token Binding + renego may be overridden at the IETF, even though it's insane. Loosening it will be a bit less of a headache if EMS can't change. https://www.ietf.org/mail-archive/web/unbearable/current/msg00690.html claims that this is already in the specification and enforced by NSS. I can't find anything to this effect in the specification. It just says the client MUST disable renegotiation when EMS is missing, which is wishful thinking. At a glance, NSS doesn't seem to check, though I could be misunderstanding the code. Nonetheless, locking this down is a good idea anyway. Accurate or not, take the email as an implicit endorsement of this from Mozilla. Change-Id: I236b05991d28bed199763dcf2f47bbfb9d0322d7 Reviewed-on: https://boringssl-review.googlesource.com/10721 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: