|author||David Benjamin <email@example.com>||Fri Jan 26 16:33:12 2018 -0500|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Fri Jan 26 21:53:27 2018 +0000|
Notice earlier if a server echoes the TLS 1.3 compatibility session ID. Mono's legacy TLS 1.0 stack, as a server, does not implement any form of resumption, but blindly echos the ClientHello session ID in the ServerHello for no particularly good reason. This is invalid, but due to quirks of how our client checked session ID equality, we only noticed on the second connection, rather than the first. Flaky failures do no one any good, so break deterministically on the first connection, when we realize something strange is going on. Bug: chromium:796910 Change-Id: I1f255e915fcdffeafb80be481f6c0acb3c628846 Reviewed-on: https://boringssl-review.googlesource.com/25424 Commit-Queue: Steven Valdez <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <firstname.lastname@example.org> Reviewed-by: Steven Valdez <email@example.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: