-
Notifications
You must be signed in to change notification settings - Fork 81
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
Need help with jruby openssl errors #141
Comments
Maybe i should try java 7 Edit: java 7 didnt help |
Hi, we can reproduce @atheiman's error as well:
JRuby
Java
OS
Note: It works on |
It seems that the Centos upgrade lost some certificates in I wonder why it does it work on MRI but not on JRuby... Both, they should use the same bundle file? Edit: Fixed file name. Thanks @wakkowarner! |
/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem dropped some SHA1 certificates. But I can't reproduce it with curl --cacert with the newer certificate file... |
a little more info here, i was just able to get this to work with a different url.
So yes it does seem like there is a change in the certs provided by the ca bundle.
https://gist.github.com/atheiman/d044bccb4744309a02886bc6190c4ee0 |
It's the 1024 bit Equifax Secure CA certificate that was removed from the ca bundle that's causing the problem. Google's GeoTrust certificates are cross signed with that old Equifax cert. See |
Can anyone with knowledge about the insides of jruby-openssl have a look at this and make it work similar to standard openssl? |
closing as it's been confirmed to be a system CA issue |
Ive been doing some work on the ruby_build chef cookbook and having trouble with openssl on jruby-9.1.13.0 on centos 6, 7, and fedora latest.
Jruby seems to install just fine but not have a ca-bundle? Basically, my failing test is checking the following:
If i run that on an instance, I get an error like:
Also,
OpenSSL::X509::DEFAULT_CERT_FILE
isnil
when I launchjirb
andrequire 'openssl'
, even if Iexport SSL_CERT_FILE=/etc/pki/tls/certs/ca-bundle.crt
Im just looking for anyway to make this test pass, but ideally the user shouldn't have to run a command before
ruby
to make openssl workWant to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: