From : Emily Stark < : Emily Stark < estark@google.com



Message-ID : <CAPP_2SaTBCsrKu5kJR5cpByV2Dyw=gXx0ia5NHG3NL2NAsLnHg@mail.gmail.com>

To : WebAppSec WG < : WebAppSec WG < public-webappsec@w3.org

Cc : Mike West < : Mike West < mkwst@google.com >, Joe DeBlasio < jdeblasio@chromium.org >, cthomp@chromium.org



Hi webappsec friends, Over in Chrome land, we've been considering how to drive down non-secure downloads, particularly high-risk ones like executables. I wanted to see if other browsers would be interested in joining us on this adventure. We want to achieve the right balance between compatibility/user-disruption and security improvements, so we will likely start by treating certain high-risk downloads initiated from secure contexts as active mixed content and block them. We're still finalizing our metrics before we can share them publicly, but right now it's looking like it will be feasible to block a set of high-risk filetypes (executables and archives as determined by the Content-Type header or sniffed mime-type). We will likely focus on protecting desktop users because Android and Safe Browsing already provide protection <https://source.android.com/security/reports/Google_Android_Security_2018_Report_Final.pdf> against malicious APKs. We're not planning to focus on non-secure downloads initiated from non-secure contexts at the moment, because users at least see the "Not Secure" omnibox badge on those pages. Feedback welcome! Thanks, Emily