| commit | 98b4cdba1e4ede26d845bcae8185ddb5b2feea93 | [log] [tgz] |
|---|---|---|
| author | Matthew Braithwaite <mab@google.com> | Mon Jan 13 15:00:30 2020 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 15 21:36:18 2020 +0000 |
| tree | 485b09a562fd69967558f593f4d2ec299c05ec7d | |
| parent | 0dcc6e231d36e41a1f2d07d1aa0094846d684099 [diff] |
Proxy: send whole SSL records through the handshaker. In split handshake tests, it is already the case that the handshaker must signal the proxy when it wants to read more data. But there was not a lot of specificity about exactly how much data would be read. The case of rejecting early data sent with a second ClientHello, following a HelloRetryRequest,[1] requires this to be nailed down, in order that the handshaker should not process the early data. This commit changes the handshaker to read exactly one SSL record and then stop, when it is asked to read. The pattern of I/O operations remains undefined. [1] See SkipEarlyData-SecondClientHelloEarlyData-TLS13-Split. Change-Id: I30f58e57fc5ebff3f7c7ef8482cc629e42fef6a4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39524 Commit-Queue: Matt Braithwaite <mab@google.com> Reviewed-by: David Benjamin <davidben@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.
Project links:
There are other files in this directory which might be helpful: