|author||David Benjamin <firstname.lastname@example.org>||Tue Nov 17 22:32:50 2015 -0500|
|committer||Adam Langley <email@example.com>||Thu Nov 19 01:23:49 2015 +0000|
Switch the keylog BIO to a callback. The keylog BIO is internally synchronized by the SSL_CTX lock, but an application may wish to log keys from multiple SSL_CTXs. This is in preparation for switching Chromium to use a separate SSL_CTX per profile to more naturally split up the session caches. It will also be useful for routing up SSLKEYLOGFILE in WebRTC. There, each log line must be converted to an IPC up from the renderer processes. This will require changes in Chromium when we roll BoringSSL. BUG=458365,webrtc:4417 Change-Id: I2945bdb4def0a9c36e751eab3d5b06c330d66b54 Reviewed-on: https://boringssl-review.googlesource.com/6514 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: