| commit | 6752efdeafeeda6156fb1ebe30db0429cc71adb6 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Jan 02 08:56:47 2017 -0500 |
| committer | Adam Langley <agl@google.com> | Thu Jan 19 23:03:11 2017 +0000 |
| tree | 3d2fc3a56cd618195f5a91b28d046495acf67e9a | |
| parent | a8c8b387f1987b4fd8d79f634be9e0a413c75ca1 [diff] |
Never send SNI warning alerts. TLS 1.3 forbids warning alerts, and sending these is a bad idea. Per RFC 6066: If the server understood the ClientHello extension but does not recognize the server name, the server SHOULD take one of two actions: either abort the handshake by sending a fatal-level unrecognized_name(112) alert or continue the handshake. It is NOT RECOMMENDED to send a warning-level unrecognized_name(112) alert, because the client's behavior in response to warning-level alerts is unpredictable. The motivation is to cut down on the number of places where we send non-closing alerts. We can't remove them yet (SSL 3.0 and TLS 1.3 draft 18 need to go), but eventually this can be a simplifying assumption. Already this means DTLS never sends warning alerts, which is good because DTLS can't retransmit them. Change-Id: I577a1eb9c23e66d28235c0fbe913f00965e19486 Reviewed-on: https://boringssl-review.googlesource.com/13221 Reviewed-by: Adam Langley <agl@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: