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
{{ message }}
Repository navigation
BCrypt::Errors::InvalidSalt: invalid salt when moving data generated by 2.1.4 to 3.0.1 #38
Hello,
I ran head-first into this issue this morning when migrating user data from an app that used bcrypt 2.1.4 to an app that uses bcrypt 3.0.1. It appears the old salts are 20 characters long while the salts generated by 3.0.1 are 29 characters. I'm not sure if there are other differences in format as well. I saw in the changelog that version 3.0.0 moved to a different underlying implementation and I wonder if that's the source issue?
At any rate, I can't seem to find any documentation for migrating salts to the current version. Any assistance would be greatly appreciated.
same problem here, but i suspect there will no way to migrate salts to the new format? if this is true it means all users have to reset their passwords?
Hello, is this issue still relevant? 3.0.0 released 12 years ago. I doubt solution for this migration problem with come if It wasn't solved in 10+ years.
Activity
emiltin commentedon Mar 30, 2012
same problem here, but i suspect there will no way to migrate salts to the new format? if this is true it means all users have to reset their passwords?
emiltin commentedon Mar 30, 2012
is there a way to just keep using the old salts?
tmm1 commentedon Mar 31, 2013
Did you find a solution to this?
micwoj92 commentedon May 26, 2024
Hello, is this issue still relevant? 3.0.0 released 12 years ago. I doubt solution for this migration problem with come if It wasn't solved in 10+ years.