commit | 5b220ee70df2de898ec55e79a6824e85479fe1c5 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Fri May 11 00:54:42 2018 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon May 14 19:10:48 2018 +0000 |
tree | aae96cb87d8565a5cbd862b23213da751c4140f8 | |
parent | 69271b5d4fed328eb61b86b013937ce22549fee5 [diff] |
Add APIs to query authentication properties of SSL_SESSIONs. This is so Chromium can verify the session before offering it, rather than doing it after the handshake (at which point it's too late to punt the session) as we do today. This should, in turn, allow us to finally verify certificates off a callback and order it correctly relative to CertificateRequest in TLS 1.3. (It will also order "correctly" in TLS 1.2, but this is useless. TLS 1.2 does not bind the CertificateRequest to the certificate at the point the client needs to act on it.) Bug: chromium:347402 Change-Id: I0daac2868c97b820aead6c3a7e4dc30d8ba44dc4 Reviewed-on: https://boringssl-review.googlesource.com/28405 Commit-Queue: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Steven Valdez <svaldez@google.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: