| commit | 0efa7592e3fb2ae647518a82ab19679b7c933d99 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jan 27 20:51:33 2017 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Feb 02 17:49:44 2017 +0000 |
| tree | 98741f786802d19c5a3554c7fbfc08daf367d444 | |
| parent | e79fe70be9b2fa2fdab00456c48f04783236fbe5 [diff] |
dispatch_alert is not an incidental write. It is impossible to have to call dispatch_alert when writing application data. Now that we don't send warning alerts through ssl3_send_alert, all alerts are closure alerts, which means attempts to write will fail. This prunes a lot of dead code, avoiding the re-entrancy in the write path. With that gone, tracking alert_dispatch is much more straightforward. BUG=146 Change-Id: Ie5fe677daee71e463d79562f3d2cea822a92581d Reviewed-on: https://boringssl-review.googlesource.com/13500 CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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.
There are other files in this directory which might be helpful: