|author||David Benjamin <email@example.com>||Mon Nov 02 17:50:10 2015 -0500|
|committer||Adam Langley <firstname.lastname@example.org>||Mon Nov 02 23:17:24 2015 +0000|
Don't use ssl3_write_pending in DTLS. That function doesn't do anything useful for DTLS. It's meant for tracking the rest of the record we've already committed to by writing half of one. But one cannot write half a datagram, so DTLS never tracks this. Just call ssl_write_buffer_flush straight and don't touch wpend_*. Change-Id: Ibe191907d64c955c7cfeefba26f5c11ad5e4b939 Reviewed-on: https://boringssl-review.googlesource.com/6418 Reviewed-by: Adam Langley <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: