-
-
Notifications
You must be signed in to change notification settings - Fork 925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenSSL ciphers with Mozilla's "Modern" set are... limited #2194
Comments
Testing all ciphers defaulting under TLSv1 while trying to find any cipher that works in JRuby/BouncyCastle against google (and other) web servers.
|
Is this addressed by #1768 ? |
@untergeek 1.7.17 still shows a small set of ciphers under Mozilla's modern cipher set:
I'll take a peak at this in the next few weeks if I can. |
@jordansissel @untergeek #1768 was not fixed in 1.7.17, I believe it was mistakenly closed. Further #1768 is about a bug in jruby-openssl's processing of a cipher spec. I believe you may be interested in: #1774 #1738 and #1737 |
@aetherknight indeed! I'm hoping to spend some quality time fixing this soon. Depends on how other logstash work goes, but we can invest energy to make this better :) |
Backround: I am trying to ship a library that supports TLS, but I want to ship with strong default security settings. I am also not a TLS expert.
Mozilla maintains a recommendation set for various security levels. Their "modern" one is documented here: https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility
If I use this cipher suite in JRuby, it basically whittles down the acceptable ciphers to just two. Two is... small. So small, that when I try connecting to https://google.com/ the ssl handshake fails because (I think) this cipher suite selection isn't supported by Google's servers.
If I compare MRI 2.1.4 on OSX 10.9 with Jruby 1.7.16.1 on OpenJDK 1.7.0_45, MRI has many ciphers, JRuby has 2 left.
I'm not certain what the right solution is here, or how to resolve this effectively, but it seems weird :)
The text was updated successfully, but these errors were encountered: