You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JRuby 1.7.12, as well as the current tip of JRuby's master branch, supports setting the ssl protocol version to TLS 1.1. However, it does not refer to the protocol in the same way that MRI's OpenSSL library does.
MRI 2.0 and later refer to TLS 1.1 and TLS 1.2 as :TLSv1_1 and :TLSv1_2, respectively. MRI 1.9.3 does not support either of these, but JRuby supports TLS 1.1 as :"TLSv1.1", requiring different symbols/strings to refer to TLS 1.1 depending on the chosen Ruby implementation.
An easy fix would be for JRuby support both :TLSv1_1 and :"TLSv1.1".
fixed on jruby-openssl 0.9.7 ... TLSv1_1 can be set (there's likely still an issue with the resolved cipher list being a bit small, please refer to #2194)
JRuby 1.7.12, as well as the current tip of JRuby's master branch, supports setting the ssl protocol version to TLS 1.1. However, it does not refer to the protocol in the same way that MRI's OpenSSL library does.
MRI 2.0 and later refer to TLS 1.1 and TLS 1.2 as :TLSv1_1 and :TLSv1_2, respectively. MRI 1.9.3 does not support either of these, but JRuby supports TLS 1.1 as :"TLSv1.1", requiring different symbols/strings to refer to TLS 1.1 depending on the chosen Ruby implementation.
An easy fix would be for JRuby support both
:TLSv1_1
and:"TLSv1.1"
.Split off of #1733
Expected behavior
Observed behavior
The text was updated successfully, but these errors were encountered: