4 ms·
That's not how I read it. The nonsecure download from a secure page is their starting point. The end goal is to block all unsecure downloads of high risk types
by PretzelFisch 8y ago
That's not how I read it. The nonsecure download from a secure page is their starting point. The end goal is to block all unsecure downloads of high risk types.
- toomuchtodo 8y agoIs it possible to disallow all non secure/https requests in Chrome?
- A2017U1 8y agoThe EFF's httpseverywhere extension works well, you need to set it to block if it can't upgrade the connection to tls
- Someone1234 8y agoGreat concept but the plugin is an absolute memory hog, and they've been unable to fix it. They closed the old bug for no real reason: https://github.com/EFForg/https-everywhere/issues/1775 https://github.com/EFForg/https-everywhere/issues/1775 Then let the new bug rot: https://github.com/EFForg/https-everywhere/issues/12232 https://github.com/EFForg/https-everywhere/issues/12232 They've now started deleting new comments on the new bug. I'm just not using it anymore.
- sucrose 8y agoThe DuckDuckGo Privacy Essentials¹ extension is a great alternative that I switched to. ¹ https://chrome.google.com/webstore/detail/duckduckgo-privacy-essent/bkdgflcldnnnapblkhphbgpggdiikppg https://chrome.google.com/webstore/detail/duckduckgo-privacy...
- Sahhaese 8y agoThe easiest way to do that is to use your OS provided firewall to block all outgoing HTTP requests from chrome and only allow HTTPS.
- gambler 8y agoThat's how I read it as well. Boiling the frogs.