New password hashing scheme: PBKDF2 #54
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SCG82
force-pushed
the
newhash
branch
2 times, most recently
from
4539196 to
8df4718
Compare
|
I've incorporated similar changes in my new release of nogin, a fork of node-login. (Mentioning as there has been no activity or responses here.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fully backwards compatible. New user passwords will be hashed using PBKDF2 (10000 iterations, sha256, 16 byte salt) and stored in MongoDB (hash length 32) along with a pass_ver field (pass_ver = 1). Users with no pass_ver field (or pass_ver = 0) will be validated using MD5. I have been using this exact code in production with 1000+ users.