|author||David Benjamin <email@example.com>||Sat Oct 17 12:43:36 2015 -0400|
|committer||Adam Langley <firstname.lastname@example.org>||Tue Oct 20 18:42:15 2015 +0000|
Deprecate SSL_want*. This is redundant with SSL_get_error. Neither is very good API, but SSL_get_error is more common. SSL_get_error also takes a return code which makes it harder to accidentally call it at some a point other than immediately after an operation. (Any other point is confusing since you can have SSL_read and SSL_write operations going on in parallel and they'll get mixed up.) Change-Id: I5818527c30daac28edb552c6c550c05c8580292d Reviewed-on: https://boringssl-review.googlesource.com/6294 Reviewed-by: Adam Langley <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: