| commit | 0b1bb12ce806e69a99ff48e01dd7d1069ca0b173 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Jan 28 14:32:53 2017 -0500 |
| committer | Adam Langley <agl@google.com> | Thu Feb 02 17:52:07 2017 +0000 |
| tree | e12415e8565196291c90f746da001ce4b8299ede | |
| parent | 0efa7592e3fb2ae647518a82ab19679b7c933d99 [diff] |
Push the SSL_CTX session_timeout zero logic up. This special-case is almost unexposed (the timeout is initialized to the default) except if the caller calls SSL_CTX_set_timeout(0). Preserve that behavior by mapping 0 to SSL_DEFAULT_SESSION_TIMEOUT in SSL_CTX_set_timeout but simplify the internal state. Change-Id: Ice03a519c25284b925f1e0cf485f2d8c54dc5038 Reviewed-on: https://boringssl-review.googlesource.com/13502 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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: