-
Notifications
You must be signed in to change notification settings - Fork 30
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
sha1 not fully secure #9
Comments
Go ahead, if nobody else is interested I am :) |
Was this ever done? |
Not yet, been too busy. So someone else is still welcome to pick it up if they desire. :) It's fairly straightforward. |
@CaptSaltyJack @aydreeuhn - have switched over from SHA1 to SHA512. |
Nice work! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SHA1 is not really a good option for password hashing. SHA512 should be used instead. Of course I'm happy to fork create a pull request if that's cool.
The text was updated successfully, but these errors were encountered: