|author||David Benjamin <firstname.lastname@example.org>||Thu Oct 31 14:50:38 2019 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Oct 31 19:20:03 2019 +0000|
Discard user_canceled alerts in TLS 1.3. Warning alerts do not exist in TLS 1.3, but RFC 8446 section 6.1 continues to define user_canceled as a signal to cancel the handshake, without specifying how to handle it. JDK11 misuses it to signal full-duplex connection close after the handshake. As a workaround, skip user_canceled as in TLS 1.2. This matches NSS and OpenSSL. Bug: b/135941563 Change-Id: I7ef546f1f166741b9f112686c75e6757331948f0 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38605 Commit-Queue: David Benjamin <email@example.com> Commit-Queue: Adam Langley <firstname.lastname@example.org> Reviewed-by: Adam Langley <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: