| commit | 3d9705d0a468405f0af392bdc53d7c40fa1e42e4 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun May 06 02:45:47 2018 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon May 07 19:05:00 2018 +0000 |
| tree | ec6019e9d3eb68c19c7d279de1f6a99e27737959 | |
| parent | 28385db6e1e480815f72f9629fa9dab48b453399 [diff] |
Fix bssl handling of buffered read data. If the peer sends us one record that exceeds buffer, the socket will no longer flag as readable, because data has been consumed, but SSL_read should still be called to drain data. bssl would instead not notice and only surface the data later on. This can (currently) be reproduced by sending "HEAD / HTTP/1.1" to www.google.com. Change-Id: I73cdbe104ba6be56fc033429999e630f0eb852d8 Reviewed-on: https://boringssl-review.googlesource.com/28166 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: 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: