| commit | bf48364a8c2ccbb9b3609727b628c2e1f1ed12bd | [log] [tgz] |
|---|---|---|
| author | Alessandro Ghedini <alessandro@ghedini.me> | Tue Nov 22 18:56:46 2016 +0000 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Dec 01 21:01:30 2016 +0000 |
| tree | 62681558ce087f528003c7ea1401be7976e02387 | |
| parent | 15073af5b7c311989f9621579b578afe1abe8fc4 [diff] |
Support setting per-connection default session lifetime value Due to recent changes, changing the SSL session timeout from cert_cb is not possible anymore since the new |SSL_SESSION| is initialized *after* cert_cb is run. The alternative would be using |SSL_CTX_set_timeout| but the specific |SSL_CTX| could be shared by multiple |SSL|s. Setting a value on a per-connection basis is useful in case timeouts need to be calculated dynamically based on specific certificate/domain information that would be retrieved from inside cert_cb (or other callbacks). It would also be possible to set the value to 0 to prevent session resumption, which is not otherwise doable in the handshake callbacks. Change-Id: I730a528c647f83f7f77f59b5b21d7e060e4c9843 Reviewed-on: https://boringssl-review.googlesource.com/12440 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: