Re:Deprecating Non-Secure HTTP
by unethical_ban on Thursday April 30, 2015 @08:03PM
(#9468431)
The actions Mozilla proposes sound awful. I believe that a secure (from the NSA) Internet is the way forward. But this seems so goofy to me. There are legitimate reasons for a site not to be hosted on HTTPS.
As you say: Color-code sites with a bit more granularity. Don't cripple the cleartext web.
[ Parent
| on HN ]
What part of this proposal made it seem like static sites with non-critical info would be "crippled" over HTTP?
Static sites or non-critical info! "Gradually phasing out access to browser features for non-secure websites, especially features that pose risks to users’ security and privacy" could affect sites that don't expose critical info.
All browsing behavior can be used to build a profile about someone, whether for advertising, surveillance, or whatever. There's a lot more information in the fact that person A visited pages 1-6 on unencrypted website B than one might realize. This reason alone should be enough for us to demand encryption (not necessarily via CA certificates) for any connection that isn't demonstrably local and unintercepted.
How does that go away? Most internet advertising/surveillance is performed by the actor with whom you're directly communicating, I think....