-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Suggestion: change password hashing from pbkdf2 to bcrypt #5859
Comments
For a compatible implementation, we can add a config option to define hash functions. Default is pbkdf2 and you can use bcrypt. |
@EpicCoder could you send a PR to do that? |
The config option is a good idea. Yes I will working on this and send a PR soon |
If you are going to do this I would suggest moving beyond bcrypt as well and add options for scrypt and argon2 as well. Short on the different algorithms: Choice is always good and these are all good choices depending on what situation you are in. A password hash that specifies the algorithm and config for it is a great idea and would allow one to change on the fly when the circumstances change. |
Last week I migrated from GitLab to gitea but had problems with the password hashes. GitLab uses 'bcrypt' and gitea uses 'pbkdf2' so I needed to modify gitea to work with 'bcrypt' and now it works fine.
Today I read that GitHub also uses 'bcrypt' for password hashing, so I think it would maybe better to move to 'bcrypt' so it's easier to migrate between different platforms.
The text was updated successfully, but these errors were encountered: