|author||David Benjamin <firstname.lastname@example.org>||Thu Jan 07 12:37:41 2016 -0800|
|committer||David Benjamin <email@example.com>||Tue Jan 26 21:51:02 2016 +0000|
Add a SSL_get_pending_cipher API. Conscrypt needs to, in the certificate verification callback, know the key exchange + auth method of the current cipher suite to pass into X509TrustManager.checkServerTrusted. Currently it reaches into the struct to get it. Add an API for this. Change-Id: Ib4e0a1fbf1d9ea24e0114f760b7524e1f7bafe33 Reviewed-on: https://boringssl-review.googlesource.com/6881 Reviewed-by: David Benjamin <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: