|author||Matthew Braithwaite <email@example.com>||Tue Nov 26 18:00:21 2019 -0800|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Mon Dec 16 23:05:32 2019 +0000|
TLS 1.3 split handshake initial support. This does not change the wire format for any existing (TLS 1.2 and lower) cases, which means it should not affect interoperability of anything that exists. Most tests pass, but I'll land those in a separate commit, after nailing down some loose ends, and in order to have more time to reason about interoperability effects. Some features are not supported yet, e.g early data. Change-Id: I7bb377017324cb3d98df75c5d6ed4757c6901ed7 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38926 Reviewed-by: David Benjamin <firstname.lastname@example.org> Reviewed-by: Adam Langley <email@example.com> Commit-Queue: Matt Braithwaite <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: