|author||David Benjamin <email@example.com>||Sat Oct 03 10:49:20 2015 -0400|
|committer||Adam Langley <firstname.lastname@example.org>||Tue Oct 13 18:18:40 2015 +0000|
Better document the callbacks around client certificates. Deprecate the client_cert_cb variant since you can't really configure intermediates with it. (You might be able to by configuring the intermediates without the leaf or key and leaving the SSL stack to configure those, but that's really weird. cert_cb is simpler.) Also document the two functions the callbacks may use to query the CertificateRequest on the client. Change-Id: Iad6076266fd798cd74ea4e09978e7f5df5c8a670 Reviewed-on: https://boringssl-review.googlesource.com/6092 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: