| commit | e52f4c46421b57c1ff4a378136ba32ae8bd3d5d9 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Oct 01 22:35:10 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Oct 09 21:53:33 2017 +0000 |
| tree | 9abdebd8c669ecf5dd415568d9578749a87816b3 | |
| parent | b25a8999be9b0e9b95624a927791cc74e862695e [diff] |
Replay the entire error queue on ssl_hs_error. This is analogous to the Go stack's handshakeErr field. Since it's quite common for callers to run two I/O operations in parallel[*] like SSL_read and SSL_write (or SSL_read and SSL_do_handshake for client 0-RTT). Accordingly, the new handshake state machine jams itself up on handshake error, but to fully work with such callers, we should also replay the error state. This doesn't yet catch all cases (there are some parts of the read flow which need to be fixed). Those will be resolved in later changes. [*] Not actually in parallel, of course, but logically in parallel on a non-blocking socket. Bug: 206 Change-Id: I5a4d37a258b9e3fc555b732938b0528b839650f8 Reviewed-on: https://boringssl-review.googlesource.com/21285 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Steven Valdez <svaldez@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: