| commit | f4654610623397339cfbd86783c765104ea09d3a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Mar 02 18:47:12 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Mar 03 02:17:31 2017 +0000 |
| tree | 0dedb1ce532cefd9737869d9c3cc0708ca65cfde | |
| parent | 924a352d1bcb6908704803c65f4d4d6fe28e47bf [diff] |
Add SSL_get0_peer_certificates. This adds a CRYPTO_BUFFER getter for the peer certificate chain. Other things we need for Chromium: - Verification callback. Ultimately, we want an asynchronous one, but a synchronous one will do for now. - Configure client cert chain without X509 I've also removed the historical note about SSL_SESSION serialization. That was years ago and we've since invalidated all serialized client sessions. BUG=671420 Change-Id: I2b3bb010f9182e751fc791cdfd7db44a4ec348e6 Reviewed-on: https://boringssl-review.googlesource.com/14065 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: