3 ms·
Why on earth would I serve a blog of lolcats over HTTPS? Or really any site that doesn't involve logins, passwords, accounts, or sensitive data of any kind?
by crazygringo 13y ago
Why on earth would I serve a blog of lolcats over HTTPS?
Or really any site that doesn't involve logins, passwords, accounts, or sensitive data of any kind?
- deleted 13y ago[deleted]
- vacri 13y agoPresumably your lolcat blog still has an admin login, and in the spirit of the first part of the article, even this would be HTTPS'd.
- rakoo 13y agoI, as a potential target for Mitm, would like to be sure that what I'm accessing is your blog, and not some phishing crap.
- rythie 13y agoISPs or anyone could still insert malicious javascript into your site, or present download buttons or login features on your site. Visits to your site could be logged by IT departments, getting your users in trouble. Also I've actually heard of places where port 80 is actually blocked by default (but 443 isn't) and you need permission on a site by site basis to get it unblocked.
- dredmorbius 13y agoI've actually heard of places where port 80 is actually blocked by default That's impressive.
- willnorris 13y agobecause if security and privacy is only limited to sensitive or controversial sites, then the use of security and privacy become suspect. If ALL internet traffic were encrypted, it would make surveillance that much more difficult because you can't find the signal in the noise. Cory Doctorow's book, Little Brother, talks a bit about this... in fact, that book was one of the motivations for Google starting to encrypt web search traffic years ago. (more of my own writing on the topic: https://willnorris.com/tag/https https://willnorris.com/tag/https)