Skip to content
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

Six Tests Failing on JRuby because of OpenSSL issue #14

Open
harrisj opened this issue Sep 25, 2015 · 2 comments
Open

Six Tests Failing on JRuby because of OpenSSL issue #14

harrisj opened this issue Sep 25, 2015 · 2 comments

Comments

@harrisj
Copy link

harrisj commented Sep 25, 2015

There is an issue with one of the cipher types and JRuby that causes six tests to fail with the same data hash wrong exception like this

  1) Xmlenc::Algorithms::RsaOaepMgf1p decrypt decrypts the cipher value
     Failure/Error: expect(subject.decrypt(cipher_value)).to be == key
     OpenSSL::PKey::RSAError:
       data hash wrong
     # ./lib/xmlenc/algorithms/rsa_oaep_mgf1p.rb:12:in `decrypt'
     # ./spec/lib/xmlenc/algorithms/rsa_oaep_mgf1p_spec.rb:14:in `(root)'

This seems to be an issue with the default JRuby SSL library, and has been patched in the distinct jruby-ssl, but I don't know enough about the issue to either change any dependencies for this gem or make a fix in my local environment to confirm that resolves the issue. I'm noting it here in case you want to investigate or offer and guidance to JRuby users affected by this problem. Thank you.

@benoist
Copy link
Contributor

benoist commented Sep 26, 2015

I wouldn't mind changing the dependency for JRuby. So if adding the jruby-ssl gem to the gemspec solves the issues I'm fine with it :)

@harrisj
Copy link
Author

harrisj commented Sep 27, 2015

I haven't really figured out what solves the issue to be honest. This is
starting to get out of my comfort zone

Sent from my iPhone

On Sep 26, 2015, at 1:11 PM, benoist [email protected] wrote:

I wouldn't mind changing the dependency for JRuby. So if adding the
jruby-ssl gem to the gemspec solves the issues I'm fine with it :)


Reply to this email directly or view it on GitHub
#14 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants