|author||Adam Langley <email@example.com>||Fri Jan 26 09:14:30 2018 -0800|
|committer||Adam Langley <firstname.lastname@example.org>||Wed Jan 31 22:24:17 2018 +0000|
Add initial, experimental support for split handshakes. Split handshakes allows the handshaking of a TLS connection to be performed remotely. This encompasses not just the private-key and ticket operations – support for that was already available – but also things such as selecting the certificates and cipher suites. The the comment block in ssl.h for details. This is highly experimental and will change significantly before its settled. Change-Id: I337bdfa4c3262169e9b79dd4e70b57f0d380fcad Reviewed-on: https://boringssl-review.googlesource.com/25387 Reviewed-by: Adam Langley <email@example.com> Commit-Queue: Adam Langley <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: