-
Notifications
You must be signed in to change notification settings - Fork 59
Add rolling option #19
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
base: main
Are you sure you want to change the base?
Conversation
It probably makes sense to have a BCrypt cryptor now to be able to migrate from sha1 or any encryptor from this gem to the "new encryptor" that Devises uses these days. If we agree in this PR, I can do another one to be able to support that rolling or even include in this one. |
Merging #20 we can rebase this to merge cleanly. |
5f7ca3f
to
ceb9c5a
Compare
@sobrinho This is awesome. Any chance of this making it into a release? Would love to be able to roll from ref: https://www.monterail.com/blog/more-secure-passwords-bcrypt |
ad3c062
to
81fbeb3
Compare
PR updated. |
@carlosantoniodasilva thoughts? |
@sobrinho This is great. Is there any interest in merging this one ? We would love to have this option to move from |
81fbeb3
to
64a8bb6
Compare
PR rebased! The build is broken for another reason on 3.0 rails main and 2.7 rails main. @carlosantoniodasilva feel free to merge this one! |
Legacy applications want to migrate from SHA1 to SHA512, for example.
Inspired in what Authlogic has with
transition_from_crypto_providers
.