commit | 31aad2dc2cc55809cb3c3e46e4fb77d1d39a6671 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Fri Oct 06 16:04:06 2017 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Oct 17 16:05:41 2017 +0000 |
tree | 197b5ca0246229977a992f71b7bd5f225c33bf59 | |
parent | f8de2af7e319f83ba88579fbf127ba5fafc26c71 [diff] |
Make low-level record errors idempotent. Enough were to make record processing idempotent (we either consume a record or we don't), but some errors would cause us to keep processing records when we should get stuck. This leaves errors in the layer between the record bits and the handshake. I'm hoping that will be easier to resolve once they do not depend on BIO, at which point the checks added in this CL may move around. Bug: 206 Change-Id: I6b177079388820335e25947c5bd736451780ab8f Reviewed-on: https://boringssl-review.googlesource.com/21366 Commit-Queue: Steven Valdez <svaldez@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: