|author||David Benjamin <email@example.com>||Thu Oct 26 19:59:58 2017 -0400|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Fri Oct 27 14:36:37 2017 +0000|
Revert "Pack encrypted handshake messages together." This reverts commit 75d43b5785bf515ebc11905c39f8c01ca30db5bf. Chatting with EKR, there is some reason to believe that doing this might cause more middlebox issues. Since we're still in the middle of working towards viable deployment in the first place, revert this. We can experiment with this later. I should have arranged for this to be controlled more carefully anyway. Change-Id: I0c8bf578f9d7364e913894e1bf3c2b8123dfd770 Reviewed-on: https://boringssl-review.googlesource.com/22204 Reviewed-by: Steven Valdez <firstname.lastname@example.org> Commit-Queue: David Benjamin <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.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: