7 ms·
> If you're not doing anything requiring security, you don't need HTTPS, IMHO. No, no, no, no, no, no, no. ALL Web traffic should be https (or http/2 or /3).
by bitwize 4y ago
> If you're not doing anything requiring security, you don't need HTTPS, IMHO.
No, no, no, no, no, no, no.
ALL Web traffic should be https (or http/2 or /3). If you connect to a site that uses insecure http, ANY link between you and that site can easily snoop on traffic and even inject different content. You CANNOT be sure that the content you see is what was originally served by the server, and you can certainly expect that state actors will be noting that you viewed this content, and building a profile on you based on that information.
- verisimilitudes 4y agoHey, fellow genius on Hacker News, do note that TLS doesn't protect against state actors, because they can very easily manipulate certificate authorities, and a malicious certificate authority completely removes most protections TLS supposedly provides.
- foverzar 4y agoIt could, if the CAs were globally distributed. Unfortunately currently they are all under the US influence.
- tsimionescu 4y agoIt's enough to compromise one CA for TLS to be entirely defeated - any CA can sign a certificate for any site, and TLS implementations will accept it. The only defense is pinned certificates, but that comes with its own problems.
- Avamander 4y agoCertificate Transparency is enforced, so it'd be quite easy to detect that compromise by now.
- tsimionescu 4y agoSure, but still somewhat after the fact.
- yardstick 4y agoHave you considered disabling non-https in your browser, and blocked outbound port 80 on your home router?
- Handytinge 4y agoFirmly disagree. Anyone can use any protocol they wish to, that's the beauty of the internet.