-
Notifications
You must be signed in to change notification settings - Fork 687
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
Use passlib for password hashing #2918
Comments
The migration functionality is very handy, also While it isn't incredibly pressing yet, our scrypt parameters for password hashing are starting to show some age, specifically N which we have currently set to |
May I work on this? |
@Aniq55 absolutely yes :-) |
@Aniq55 Any update on this? |
Note that this is blocked by #1419 |
@kushaldas I'm on a break currently. You may unassigned me for now. :/ |
@Aniq55 consider yourself unassigned, thanks for the update. |
@dachary can i take this up.. |
@pwnchief As mentioned above, this is blocked by #1419 (which I'm getting to), but that ticket itself is blocked by at least #3033 and #2948. It will probably be a long while before we can merge anything you work on. I don't want to discourage you, but it can be disheartening to work on something and have the PR sit open for months. |
Ohhhhh okay thanks for the recommendation. I will wait for the labels to clear up... |
It requires
|
Feature request
Description
Using
passlib
for password hashing will give us future proof and easily migrateable password management should we change password hashing algorithms/parameters.Possibly conflicts with #1609 depending on what the underlying cryptolib is.
User Stories
As a dev, I don't want to have to write boilerplate migration code if we bump the number of scrypt rounds.
The text was updated successfully, but these errors were encountered: