News for hackers. Stuff that matters.
Re:HTTPS is more secure, so why isn't the Web using it? by pyre on Monday March 21, 2011 @03:15AM (#2348804)
Errr... Are we advocating HTTPS everywhere? Or just when it's time to transfer private information?

When I want to read an essay on some random website, to I need to now that the website owner is who they say that they are? Isn't self-signed HTTPS better than just plain old HTTP? Or is it better that we only use HTTPS for a select few sites that aren't self-signed and HTTP everywhere else?

Re:HTTPS is more secure, so why isn't the Web using it? by chrisbolt on Monday March 21, 2011 @03:17AM (#2348807)
If you're not transferring private information, why does it matter if it's encrypted? Either you care if someone can eavesdrop or you don't.
Re:HTTPS is more secure, so why isn't the Web using it? by fierarul on Monday March 21, 2011 @06:16AM (#2349088)
The whole online presence might be something that some regard as private since reading a given URL might be as private as a forum password or card info.

But 'either you care or you don't' seems too inflexible to me.

For example, I might care that my bank has a certificate signed by a CA.

But for some usergroup's online forum, a self-signed certificate is enough. Sure, we might get some MITM but the barrier to this is so high and the relative importance of the online forum so low, it seems an adequate trade-off. I'd say there's a higher chance of the server hard drive failing than to see an actual MITM attack on a given niche server.

But overall, as I've said in another message here, I see this whole centralized design as flawed and much too expensive. Certificate info should be a DNS attribute.

Re:HTTPS is more secure, so why isn't the Web using it? by pyre on Monday March 21, 2011 @08:49PM (#2352420)
If you only use encryption when you 'have something to hide,' then use of encryption is enough to incriminate you.