Re:A basic guide to when and how to deploy HTTPS
by rythie on Saturday December 21, 2013 @05:48PM
(#6948421)
ISPs 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.
Re:A basic guide to when and how to deploy HTTPS
by dredmorbius on Sunday December 22, 2013 @01:09PM
(#6951029)
I've actually heard of places where port 80 is actually blocked by default
That's impressive.
Re:A basic guide to when and how to deploy HTTPS
by willnorris on Sunday December 22, 2013 @03:05AM
(#6949730)
because 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)
Or really any site that doesn't involve logins, passwords, accounts, or sensitive data of any kind?