| commit | 2a0707210aec2ce3917c343ada43c27f176082d3 | [log] [tgz] |
|---|---|---|
| author | Steven Valdez <svaldez@chromium.org> | Sat Mar 25 20:54:16 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sun Mar 26 18:13:57 2017 +0000 |
| tree | 2f683b850d472d629e08c963cb09b7f5b0655ffc | |
| parent | 246eeee61a91edd953b4e58682356ba53eb4e0e0 [diff] |
Prevent Channel ID and Custom Extensions on 0-RTT. Channel ID is incompatible with 0-RTT, so we gracefully decline 0-RTT as a server and forbid their combination as a client. We'll keep this logic around until Channel ID is removed. Channel ID will be replaced by tokbind which currently uses custom extensions. Those will need additional logic to work with 0-RTT. This is not implemented yet so, for now, fail if both are ever configured together at all. A later change will allow the two to combine. BUG=183 Change-Id: I46c5ba883ccd47930349691fb08074a1fab13d5f Reviewed-on: https://boringssl-review.googlesource.com/14370 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: