| commit | 8df6766d01ab5e3097d83498a2517a1226803399 | [log] [tgz] |
|---|---|---|
| author | Alessandro Ghedini <alessandro@ghedini.me> | Mon Feb 06 13:33:51 2017 +0000 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Feb 07 17:50:13 2017 +0000 |
| tree | 379cc990246f91c312d84ead0f2560b223967073 | |
| parent | 33fe4a0d1406f423e7424ea7367e1d1a51c2edc1 [diff] |
Support setting per-connection SCT list Right now the only way to set an SCT list is the per-context function SSL_CTX_set_signed_cert_timestamp_list. However this assumes that all the SSLs generated from a SSL_CTX share the same SCT list, which is wrong. In order to avoid memory duplication in case SSL_CTX has its own list, a CRYPTO_BUFFER is used for both SSL_CTX and SSL. Change-Id: Id20e6f128c33cf3e5bff1be390645441be6518c6 Reviewed-on: https://boringssl-review.googlesource.com/13642 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: