|author||David Benjamin <firstname.lastname@example.org>||Tue Dec 29 23:32:29 2015 -0500|
|committer||Adam Langley <email@example.com>||Fri Jan 15 22:09:24 2016 +0000|
Add APIs to extract the SSL key block. This is a companion to SSL_get_rc4_state and SSL_get_ivs which doesn't require poking at internal state. Partly since it aligns with the current code and partly the off chance we ever need to get wpa_supplicant's EAP-FAST code working, the API allows one to generate more key material than is actually in the key block. Change-Id: I58bc3f2b017482dbb8567dcd0cd754947a95397f Reviewed-on: https://boringssl-review.googlesource.com/6839 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: