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 uses krypt to provide pkcs5, via require 'krypt/ossl' in lib/ruby/shared/openssl.rb. However, the jruby-openssl.rb file we load from the gem does not have this line, and so OpenSSL::PKCS5 is never defined.
A workaround is to require krypt/ossl yourself.
Proper gemification of jruby-openssl would fix this, as would simply adding the require to the gem's jruby-openssl.rb file, but we also need to ensure the depdency comes along for pre-1.7 JRuby (and we should probably be treating krypt as a default gem anyway).
Unsure of the status of gemification of krypt. Can you comment, @emboss?
The text was updated successfully, but these errors were encountered:
@headius: There is a gem version published that should be equal to the version you included in JRuby. The "krypt-core" gem is also published with separate JRuby and C-based versions, so that it should work out of the box that if you do "gem install krypt" it will automatically pull in the JRuby-specific sub gems if you're on JRuby.
Would that work for you? Let me know if you want me to change anything!
Just for clarity, if you are running into this issue w/ Rails, you need to add the krypt gem to your GEMFILE as the krypt jars are no longer part of the JRuby install.
JRuby uses krypt to provide pkcs5, via require 'krypt/ossl' in lib/ruby/shared/openssl.rb. However, the jruby-openssl.rb file we load from the gem does not have this line, and so OpenSSL::PKCS5 is never defined.
A workaround is to require krypt/ossl yourself.
Proper gemification of jruby-openssl would fix this, as would simply adding the require to the gem's jruby-openssl.rb file, but we also need to ensure the depdency comes along for pre-1.7 JRuby (and we should probably be treating krypt as a default gem anyway).
Unsure of the status of gemification of krypt. Can you comment, @emboss?
The text was updated successfully, but these errors were encountered: