Added dynamics to allow for database stored parameters when using encrypted attributes in models #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…well as :public_key=>:derived to use the public key contained in the private key
…it work on my env
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added :private_key and :public_key options to AsymmetricCipher to allow for database/memory stored keys
Added :encrypt_with_private to turn around roles for private and public key
Added :public_key => :derived option for allowing the public key to be derived from the private key file
:algorithm, :password, :salt, :private_key and :public_key now support Procs for getting the values e.g. from a field in the database