Google plans to begin warning users about security risks from downloading files over non-TLS connections in April 2020. Those warnings will be gradually ratcheted up until Chrome blocks them altogether beginning in October 2020.
Today we’re announcing that Chrome will gradually ensure that secure (HTTPS) pages only download secure files. In a series of steps outlined below, we’ll start blocking “mixed content downloads” (non-HTTPS downloads started on secure pages). This move follows a plan we announced last year to start blocking all insecure subresources on secure pages.
Insecurely-downloaded files are a risk to users’ security and privacy. For instance, insecurely-downloaded programs can be swapped out for malware by attackers, and eavesdroppers can read users’ insecurely-downloaded bank statements. To address these risks, we plan to eventually remove support for insecure downloads in Chrome.
As a first step, we are focusing on insecure downloads started on secure pages. These cases are especially concerning because Chrome currently gives no indication to the user that their privacy and security are at risk
- February 9, 2020 @ 19:24:59 [Current Revision] by Brian Carnell
- February 9, 2020 @ 19:23:54 by Brian Carnell
There are no differences between the February 9, 2020 @ 19:23:54 revision and the current revision. (Maybe only post meta information was changed.)