|author||David Benjamin <email@example.com>||Fri Jul 14 18:40:34 2017 -0400|
|committer||David Benjamin <firstname.lastname@example.org>||Fri Jul 14 23:17:40 2017 +0000|
Fix handling of ServerHellos with omitted extensions. Due to SSL 3.0 legacy, TLS 1.0 through 1.2 allow ClientHello and ServerHello messages to omit the extensions field altogether, rather than write an empty field. We broke this in https://boringssl-review.googlesource.com/c/17704/ when we needed to a second ServerHello parsing path. Fix this and add some regression tests to explicitly test both the omitted and empty extensions ClientHello and ServerHello cases. Bug: chromium:743218 Change-Id: I8297ba608570238e19f12ea44a9fe2fe9d881d28 Reviewed-on: https://boringssl-review.googlesource.com/17904 Reviewed-by: David Benjamin <email@example.com> Commit-Queue: David Benjamin <firstname.lastname@example.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: