Updated match_password/encrypt_password methods to use latest secure password hashing library #99
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
…ase for validation/encryption
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.
Provider.pm was upgraded to use Crypt::Passphrase for encrypting and validating passwords. Crypt::SaltedHash remains to allow hashed passwords using previous algorithms such as
SSHA512to seamlessly migrate to more secure algorithms such asArgon2which uses Crypt::Passphrase.match_passwordnow does not just return a true/false boolean, but a hash consisting of the two boolean values: legacy, valid. If thelegacyvalue is true, the validated password is rehashed withinauthenticate_user.