11–20 of 112 posts
In case you're wondering what "Perfect Forward Secrecy" is: SSL/TLS, like most protocols, uses (expensive, dangerous) RSA to exchange (cheap, simple) AES or RC4 session keys; bulk data is encrypted with session key. In the normal protocol, if you lose the RSA key, an attacker can retroactively decrypt the session keys, which are protected only by that same RSA key. In ephemeral DH mode, instead of encrypting a sessio…
It sounds magical too.
I ran this against the slowest SSL website I know of. This site absolutely kills my phone web browser and I've been wondering about this problem for years. The site: manager.skype.com. The result? DHE-RSA-AES256-SHA. No wonder! Fix this guys! In regards to this post, if this is the default configuration of Nginx then I agree that Nginx sucks. This is not a good default configuration for the Internet.
So Nginx got unwarranted hate for having the most secure defaults. That sucks. I hope the user nginxorg -- whom I assume is Igor Sysoev -- who dropped by the previous thread ( http://news.ycombinator.com/item?id=2752136 ), sees this post too. Either way -- based on his attitude in the first post, I'm really surprised by how Matt owned up and did his homework for this one. (He should have done it from the beginning, o…
It's not the "best/most secure". All the other servers can trivially enable EDH as well; it's OpenSSL that implements it, not nginx. Reasonable people can disagree on what the right default is, but plenty of financial institutions have made the studied choice not to enable it.
openssl s_client -host HOSTNAME -port 443
I ran this for my own website and a few bigger websites
openssl s_client -host www.gusta.com -port 443 (My site, hosted on Heroku)
Cipher : DHE-RSA-AES256-SHA
openssl s_client -host www.google.com -port 443
Cipher : RC4-SHA
openssl s_client -host www.airbnb.com -port 443
Cipher : AES256-SHA
openssl s_client -host www.facebook.com -port 443
Cipher : RC4-MD5
openssl s_client -host www.paypal.com -port 443
Cipher : AES256-SHA
openssl s_client -host www.amazon.com -port 443
Cipher : RC4-MD5I ran this against the slowest SSL website I know of. This site absolutely kills my phone web browser and I've been wondering about this problem for years. The site: manager.skype.com. The result? DHE-RSA-AES256-SHA. No wonder! Fix this guys! In regards to this post, if this is the default configuration of Nginx then I agree that Nginx sucks. This is not a good default configuration for the Internet.
There's nothing wrong with using DHE algorithms, particularly if you're going to be transferring financial secrets around. If your phone can't keep up, well, then it probably should have a better entropy generator.
before: nginx (ssl) -> haproxy: 90 requests per second
after: nginx (AES256-SHA with keepalive 5 5;) -> haproxy: 4300 requests per second
I can't tell if this is an apology or a non-apology. It seems to have elements of both. Clearly the moral of the story is: "Don't claim that X sucks unless you are are damn sure". Saying something sucks is fightin' words. Don't expect to people be nice if you are wrong.
The result was his digging into it to figure out the default config included a computationally expensive setup.
That's a debatable thing. Not necessarily wrong.
So Nginx got unwarranted hate for having the most secure defaults. That sucks. I hope the user nginxorg -- whom I assume is Igor Sysoev -- who dropped by the previous thread ( http://news.ycombinator.com/item?id=2752136 ), sees this post too. Either way -- based on his attitude in the first post, I'm really surprised by how Matt owned up and did his homework for this one. (He should have done it from the beginning, o…
It's not the "best/most secure". All the other servers can trivially enable EDH as well; it's OpenSSL that implements it, not nginx. Reasonable people can disagree on what the right default is, but plenty of financial institutions have made the studied choice not to enable it.
So Nginx got unwarranted hate for having the most secure defaults. That sucks. I hope the user nginxorg -- whom I assume is Igor Sysoev -- who dropped by the previous thread ( http://news.ycombinator.com/item?id=2752136 ), sees this post too. Either way -- based on his attitude in the first post, I'm really surprised by how Matt owned up and did his homework for this one. (He should have done it from the beginning, o…
It's not the "best/most secure". All the other servers can trivially enable EDH as well; it's OpenSSL that implements it, not nginx. Reasonable people can disagree on what the right default is, but plenty of financial institutions have made the studied choice not to enable it.
Unless I'm reading OP wrong, that's not the case for the servers he uses for his tests: Stud can't enable it at all:
> stud doesn't have at all.
and in stunnel you have to compile it in for support, it's not just "not enabled by default", it's not compiled in:
> stunnel has it as a compile time/certificate configurable option.
Earlier quoted context omitted.
It's not the "best/most secure". All the other servers can trivially enable EDH as well; it's OpenSSL that implements it, not nginx. Reasonable people can disagree on what the right default is, but plenty of financial institutions have made the studied choice not to enable it.
Plenty of financial institutions have also made the studied choice to limit the length and types of characters I can use in my password.