News for hackers. Stuff that matters.
Re:SSL: Intercepted today, decrypted tomorrow by dfc on Tuesday June 25, 2013 @07:45PM (#5943210)
I have a bad habit of linking to HN posts and assuming that people understand I mean "look at the comments." The Cloudflare instructions break chrome? That is my bad, I have not verified them myself recently. I usually use the cloudflare settings or jacob's duraconf[1]. Thanks to joeyh's mr I usually have duraconf checked out on any machine that I use.

[1] https://github.com/ioerror/duraconf

Re:SSL: Intercepted today, decrypted tomorrow by jcampbell1 on Tuesday June 25, 2013 @08:04PM (#5943276)
Yes, the cloudflare advice does break chrome PFS. With the defaults, chrome shows:

    CAMELLIA_256_CBC, with SHA1 for message 
    authentication and DHE_RSA as the 
    key exchange mechanism.
By changing to the suggestion in the comments, the encryption downgrades to:

    The connection is encrypted using RC4_128,
    with SHA1 for message authentication and 
    RSA as the key exchange mechanism.
Re:SSL: Intercepted today, decrypted tomorrow by dfc on Tuesday June 25, 2013 @08:09PM (#5943301)
Yeah, I actually just noticed that cloudflare was using nginx so the qualys scan was not indicative of the cloudflare apache setup. I apologize I got distracted watching those genetic cars.
Re:SSL: Intercepted today, decrypted tomorrow by newman314 on Wednesday June 26, 2013 @03:52AM (#5944707)
See my comment in the second link for what I use for nginx. I prefer explicitly stating ciphers to make sure only the ones I want presented are used