Hardening your Web Server's SSL Ciphers

Post by hynek » Wed, Feb 06, 2013, 6:59 AM UTC

huxley wrote: post #26

hynek wrote: post #6

Earlier quoted context omitted.

Absolutely. But since we still have to support SSLv3 from 1996, I wouldn’t hold my breath. :(

Do we really? What browsers don't support at least TLS 1.0? Or is it other user agents?

It very much depends on your target audience.

We’re in the web hosting business and whenever we try to be a bit more progressive, people start yelling at us that their IE 4-using customers in rural Mongolia can’t SSL-surf their shop. When it comes to mail, IIRC some business phones were behind too.

OTOH iOS 6 support TLS 1.2, so if you’re just building a REST API for your own apps, you can go wild.

Post by newman314 » Sat, Feb 09, 2013, 7:46 PM UTC

CrLf wrote: post #17

dochtman wrote: post #9

I think this CipherSuite is actually better than what you have (and Qualys seems to think so, too): SSLCipherSuite ECDHE-RSA-AES128-SHA256:AES128-GCM-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH Also, I couldn't get your disabling of SSL compression to work (on Gentoo Linux), either by pasting the export line into /etc/conf.d/apache2 (at the end) or /etc/init.d/apache2 (at the top).

For openssl 0.9.8, where "ECDHE-RSA-AES128-SHA256" and "AES128-GCM-SHA256" aren't supported, that cipher suite actually places RC4 40bit as the preferred cipher ("openssl ciphers -v").

For that reason, I prefer to explicitly list the ciphers to be used to avoid situations like this or when OpenSSL decides to modify its cipher list.

FWIW, this is what I use:

ECDHE-RSA-AES128-GCM-SHA256:AES128-GCM-SHA256:ECDHE-RSA-RC4-SHA:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-S HA:RC4-SHA:AES128-SHA:AES256-SHA;

Re: Hardening your Web Server's SSL Ciphers

Re: Hardening your Web Server's SSL Ciphers