|author||David Benjamin <email@example.com>||Fri Oct 06 16:30:26 2017 -0400|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Tue Oct 17 15:02:21 2017 +0000|
Remove remnants of blocking DTLS timeouts. We only support non-blocking BIOs for DTLS as of https://boringssl-review.googlesource.com/13945. This logic is a remnant of that. It should not be necessary. All users of DTLSv1_get_timeout call DTLSv1_handle_timeout. This gets it out of the way for dtls_open_record calls which don't use dtls1_get_record. We can restore it elsewhere if necessary, but I don't think we need it. Change-Id: Idb737868358e4b59ad3cb2c994c7084ffcdb3709 Reviewed-on: https://boringssl-review.googlesource.com/21349 Commit-Queue: Steven Valdez <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <firstname.lastname@example.org> Reviewed-by: Steven Valdez <email@example.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: