|author||David Benjamin <firstname.lastname@example.org>||Sun Oct 18 00:00:06 2015 -0400|
|committer||Adam Langley <email@example.com>||Mon Oct 26 18:43:38 2015 +0000|
Document the rest of ssl.h. Although Chromium actually uses SSL_(get_)state as part of its fallback reason heuristic, that function really should go in the deprecated bucket. I kept SSL_state_string_long since having a human-readable string is probably useful for logging. SSL_set_SSL_CTX was only half-documented as the behavior of this function is very weird. This warrants further investigation and rethinking. SSL_set_shutdown is absurd. I added an assert to trip up clearing bits and set it to a bitwise OR since clearing bits may mess up the state machine. Otherwise there's enough consumers and it's not quite the same as SSL_CTX_set_quiet_shutdown that I've left it alone for now. Change-Id: Ie35850529373a5a795f6eb04222668ff76d84aaa Reviewed-on: https://boringssl-review.googlesource.com/6312 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: