-
Notifications
You must be signed in to change notification settings - Fork 42
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
Current state of this gem #49
Comments
Just my observation that upgrading to Ruby 2.4 breaks this gem with the following error:
The line of code that breaks is lock.rb:49 # Using a blank password in OpenSSL::PKey::RSA.new prevents reading
# the private key if the file is a key pair
public_key = get_rsa_key(@public_key,"") The double quotes is a hard coded 'password', and that is the field that is expected to be 4 bytes or longer. There does not seem to be any way to configure this or force it to use a 4 byte (or longer) password, without monkey patching the gem. Are you aware of any alternatives to this library, @ehannes , especially those which would allow us to continue using the current data in our database without a tedious decrypt/re-encrypt migration? |
I've noticed that the master branch is being updated, but there are no new releases since 2015. I am not sure about the status of the gem. Is it being mantained? |
I would say no since no maintainer has answered this question in 1,5 year :( |
What is the current state of this gem? According to the Readme:
I see there is an unmerged pull request from 2014 to update support for Rails 4.1 and Ruby 2.1. Now, Rails 5 is out. Is this gem maintained anymore?
The text was updated successfully, but these errors were encountered: