CloudFlare's internet-facing SSL cipher configuration (github.com)

Furthermore, they have great config examples for nginx and others[1] -- it's pretty easy to forget/misconfigure things like Diffie-Hellman parameters, OCSP stapling and session caching.

[1] https://wiki.mozilla.org/Security/Server_Side_TLS#Nginx

>The difficulty is that, for public web sites that need to support a wide user base, there is practically nothing 100% secure they can use to replace RC4.

Also, given the cipher preference, RC4 wont be used with modern browsers.

It's to balance the need to protect against BEAST vs RC4 issues. They use an OpenSSL patch that "disables RC4-based cipher suites for connections using TLS v1.1 and above, while leaving them there to protect users still using TLS v1.0"

I disabled all the broken crypto (RC4, RSA handshake) in my browser few months ago and everything was fine for a while. Then about 2-3 months ago Youtube\gmail started demanding RC4.

Another "funny" example of this was oculusvr.com

oculusvr.com/order/ redirects to https://www.oculusvr.com/order/

requires RC4 and RSA, doesnt like diffiehelman and AES

BUT https://support.oculusvr.com/home less critical part of the site works with more secure AES/DH

So the part of the site that deals with confidential data and money defaults to BROKEN crypto, while bugtracker works fine with secure crypto. W T F????

  Supported Server Cipher(s):
    Accepted  SSLv3  256 bits  ECDHE-RSA-AES256-SHA
    Accepted  SSLv3  256 bits  AES256-SHA
    Accepted  SSLv3  168 bits  ECDHE-RSA-DES-CBC3-SHA
    Accepted  SSLv3  168 bits  DES-CBC3-SHA
    Accepted  SSLv3  128 bits  ECDHE-RSA-AES128-SHA
    Accepted  SSLv3  128 bits  AES128-SHA
    Accepted  SSLv3  128 bits  ECDHE-RSA-RC4-SHA
    Accepted  SSLv3  128 bits  RC4-SHA
    Accepted  SSLv3  128 bits  RC4-MD5
    Accepted  TLSv1  256 bits  ECDHE-RSA-AES256-SHA
    Accepted  TLSv1  256 bits  AES256-SHA
    Accepted  TLSv1  168 bits  ECDHE-RSA-DES-CBC3-SHA
    Accepted  TLSv1  168 bits  DES-CBC3-SHA
    Accepted  TLSv1  128 bits  ECDHE-RSA-AES128-SHA
    Accepted  TLSv1  128 bits  AES128-SHA
    Accepted  TLSv1  128 bits  ECDHE-RSA-RC4-SHA
    Accepted  TLSv1  128 bits  RC4-SHA
    Accepted  TLSv1  128 bits  RC4-MD5

  Prefered Server Cipher(s):
    SSLv3  128 bits  ECDHE-RSA-RC4-SHA
    TLSv1  128 bits  ECDHE-RSA-RC4-SHA

Arguably thats also NSS's fault for implementing TLS1.2 so late, but still...

My site only gets an "A" rating, but Firefox actually connects using ECDHE-RSA-AES256-SHA. I use this cipherlist

  HIGH:!SSLv2:!aNULL:!3DES

They give back to the community and even offer free plans that are pretty damn useful.

With amount of growth they have experienced, you should be thankful that they are able to find time for anything at all at this point.

I'll see what I can do about getting this information open sourced.

[[UPDATE]] I'm hearing this is still planned, and we're aiming to get this out this coming summer. Internal projects have pushed this back a bit, apologies.

If a company says "we plan to..." then odds are they are telling the truth. At the time of writing that is exactly what they were planning to do. It turns out that sometimes plans change. Or planned things take longer than initially planned for.

But of course if you ever say anything on the internet people treat it like a promise and then you get called a liar. This is why we can't have nice things.