| commit | 11c82895d7a827afc62097210c676ae1a82abf7d | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Feb 23 20:40:31 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Mar 01 19:59:28 2017 +0000 |
| tree | b71a6b6eb91dbdd11e9447781259b6fd295681fc | |
| parent | 7e429991223e6f6ba58cd0433e245b67d7b12125 [diff] |
Remove support for blocking DTLS timeout handling. The DTLS stack has two very different APIs for handling timeouts. In non-blocking mode, timeouts are driven externally by the caller with DTLSv1_get_timeout. In blocking mode, timeouts are driven by the BIO by calling a BIO_ctrl with BIO_CTRL_DGRAM_SET_NEXT_TIMEOUT. The latter is never used by consumers, so remove support for it. BIO_CTRL_DGRAM_SET_NEXT_TIMEOUT implicitly depends on struct timeval being used for timestamps, which we would like to remove. Without this, the only public API which relies on this is the testing-only SSL_CTX_set_current_time_cb which is BoringSSL-only and we can change at our leisure. BUG=155 Change-Id: Ic68fa70afab2fa9e6286b84d010eac8ddc9d2ef4 Reviewed-on: https://boringssl-review.googlesource.com/13945 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: