|author||David Benjamin <firstname.lastname@example.org>||Tue Aug 09 16:21:24 2016 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Aug 11 00:35:31 2016 +0000|
Only have one ClientHello parser, not three. Between TLS 1.2, TLS 1.3, and the early callback, we've got a lot of ClientHello parsers. Unify everything on the early callback's parser. As a side effect, this means we can parse a ClientHello fairly succinctly from any function which will let us split up ClientHello states where appropriate. Change-Id: I2359b75f80926cc7d827570cf33f93029b39e525 Reviewed-on: https://boringssl-review.googlesource.com/10184 Reviewed-by: Adam Langley <email@example.com> Commit-Queue: Adam Langley <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <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: