|author||David Benjamin <firstname.lastname@example.org>||Sat Oct 17 23:26:35 2015 -0400|
|committer||Adam Langley <email@example.com>||Mon Oct 26 18:35:01 2015 +0000|
Document the (formerly) SSL_state wrapper macros. SSL_in_connect_init and SSL_in_accept_init are removed as they're unused both within the library and externally. They're also kind of silly. Expand on how False Start works at the API level in doing so. Change-Id: Id2a8e34b5bb8f28329e3b87b4c64d41be3f72410 Reviewed-on: https://boringssl-review.googlesource.com/6310 Reviewed-by: 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: