| commit | b5eb1958bb84e6bd94670866f83233df98e04bac | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jun 17 18:44:38 2016 -0400 |
| committer | Adam Langley <agl@google.com> | Mon Jun 27 20:08:25 2016 +0000 |
| tree | 55149d1ca9c6f4ff56d71e0990986d6f6e28bd23 | |
| parent | c42acee63d22c1a4d8f3ee648e98abfdb1341ba2 [diff] |
Make dtls1_do_handshake_write less stateful. Now dtls1_do_handshake_write takes in a serialized form of the full message and writes it. It's a little weird to serialize and deserialize the header a bunch, but msg_callback requires that we keep the full one around in memory anyway. Between that and the handshake hash definition, DTLS really wants messages to mean the assembled header, redundancies and all, so we'll just put together messages that way. This also fixes a bug where ssl_do_msg_callback would get passed in garbage where the header was supposed to be. The buffered messages get sampled before writing the fragment rather than after. Change-Id: I4e3b8ce4aab4c4ab4502d5428dfb8f3f729c6ef9 Reviewed-on: https://boringssl-review.googlesource.com/8433 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: