| commit | 700631bdf06b35b668d2b73a57e3baf63140ce03 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu May 24 17:17:34 2018 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue May 29 14:28:56 2018 +0000 |
| tree | 3b57a1c3e7224198b638e2b86d1975a6933db9dc | |
| parent | 81d4a03bb0839d89ba82c881686bd6054d8ca8eb [diff] |
Pack encrypted handshake messages together. We have a successful TLS 1.3 deployment, in spite of non-compliant middleboxes everywhere, so now let's get this optimization in. It would have been nice to test with this from the beginning, but sadly we forgot about it. Ah well. This shaves 63 bytes off the server's first flight, and then another 21 bytes off the pair of NewSessionTickets. So we'll more easily notice in case of anything catastrophic, tie this behavior to draft 28. Update-Note: This slightly tweaks our draft-28 behavior. Change-Id: I4f176a919bf7181239d6ebb31e7870f12364e0f9 Reviewed-on: https://boringssl-review.googlesource.com/28744 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: Steven Valdez <svaldez@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: