News for hackers. Stuff that matters.
Re:SSL: Intercepted today, decrypted tomorrow by gcb0 on Tuesday June 25, 2013 @06:12PM (#5942788)
So the only solution is to increase the effort to decrypt. And for that we have to either/both increase complexity of the crypto (hard) and the amount of noise traffic.

Changing the crypto would require lots of time to roll out new platforms and updated clients.

Hence, the only feasible way to save the internet is to convert all porn sites to https. If you work on a ISP, block all porn connections over http, nature will find a way and the https sites will popup overnight.

Re:SSL: Intercepted today, decrypted tomorrow by icebraining on Tuesday June 25, 2013 @06:35PM (#5942891)
With SNI[1], the hostname is sent unencrypted (so that you can host more than one domain in a single IP address), so the watchers can simply filter out porn domains.

[1] https://en.wikipedia.org/wiki/Server_Name_Indication

Re:SSL: Intercepted today, decrypted tomorrow by contingencies on Tuesday June 25, 2013 @07:10PM (#5943057)
As of November 2012, the only major user bases whose browsers do not support SNI appear to be users of Android 2.x (default browser), Internet Explorer (any version) on Windows XP and versions of Java before 1.7 on any operating system.

Apparently we can thank the French: http://www.edelweb.fr/EdelKey/

Re:SSL: Intercepted today, decrypted tomorrow by mappu on Tuesday June 25, 2013 @08:22PM (#5943346)
From a security point of view I don't think this changes anything - in the absence of SNI, you can get the hostname anyway just by starting a TLS connection to the server, as your browser would.

(Unless porn sites start whitelisting incoming IP addresses, which seems pretty unlikely)

Re:SSL: Intercepted today, decrypted tomorrow by X-Istence on Tuesday June 25, 2013 @07:14PM (#5943081)
It is sad, but by the time SNI is a viable extension to use, IPv6 should be in full swing and SNI will no longer be required :-(.
Re:SSL: Intercepted today, decrypted tomorrow by graue on Tuesday June 25, 2013 @08:19PM (#5943337)
SNI is already plenty viable if you have few/no IE users. That's certainly not everyone, but it's good enough for some of us.
Re:SSL: Intercepted today, decrypted tomorrow by bigiain on Tuesday June 25, 2013 @11:37PM (#5944039)
And while I know cPanel/WHM doesn't really belong in the same discussion as "encryption possibly resilient against state level attackers"… I note with interest that the latest cPanel update (11.38) includes SNI support. That's "switched on" an _huge_ userbase of webhosting that can now grab a cheap/free SSL cert without needing dedicated ip addresses, and who can then tell users "you'll need to upgrade your browser to use our secure site - have you tried downloading Chrome?" ;-)
Re:SSL: Intercepted today, decrypted tomorrow by sliverstorm on Tuesday June 25, 2013 @06:35PM (#5942894)
Changing the crypto would require lots of time to roll out new platforms and updated clients.

Which is just an argument for starting sooner rather than later, and staying ahead of the curve, rather than giving up the point...

Re:SSL: Intercepted today, decrypted tomorrow by gcb0 on Tuesday June 25, 2013 @09:57PM (#5943652)
couldn't agree more. was just setting the joke up. :)
Re:SSL: Intercepted today, decrypted tomorrow by fixxer on Tuesday June 25, 2013 @10:23PM (#5943769)
"nature will find a way"

brilliant statement. thank you.

Re:SSL: Intercepted today, decrypted tomorrow by 7952 on Wednesday June 26, 2013 @06:01AM (#5945096)
Or protocols need to develop that use out of band communication to seed certificates. Just mail me some entropy :)