|author||David Benjamin <email@example.com>||Wed Nov 16 19:07:53 2016 +0900|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Thu Nov 17 00:29:46 2016 +0000|
Call cert_cb before resolving resumption. This is in preparation for determining the cipher suite (which, in TLS 1.2, requires the certificate be known) before resumption. Note this has caller-visible effects: - cert_cb is now called whether resumption occurs or not. Our only consumer which uses this as a server is Node which will require a patch to fix up their mucking about with SSL_get_session. (But the patch should be quite upstreamable. More 1.1.0-compatible and generally saner.) - cert_cb is now called before new_session_cb and dos_protection_cb. BUG=116 Change-Id: I6cc745757f63281fad714d4548f23880570204b0 Reviewed-on: https://boringssl-review.googlesource.com/11846 Reviewed-by: Adam Langley <firstname.lastname@example.org> Commit-Queue: Adam Langley <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <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: