-
Notifications
You must be signed in to change notification settings - Fork 28
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
NIST-based entropy calculation should not be the default #6
Comments
Thanks for bringing this to my attention. When I was researching entropy calculation methods, I found that there are few standard methods and almost all are disputed. I chose NIST as the default simply because it had, well, NIST's stamp of approval. I'll have to do some more research on the subject and revisit this decision. I'll also look into implementing more choices in algorithm. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The wikipedia article mentions the following:
The linked blog post and research paper clarify this statement. NIST relies on the Shannon entropy model, which has been proven to incorrectly model real-world password entropy considering use by humans and real-life attack methods. Having this method as the default is therefore unwise and should be deprecated.
I'm not sure how the Wolfram Alpha calculation is constructed, so cannot say if it performs better, but from my personal tests it also has some weak spots. A method like Dropbox's zxcvbn algorithm seems to be a better match, although it hasn't been around long enough to be properly reviewed. Still it seems like a reasonable method that would be good to implement since it can be used in combination with the front-end javascript library. Something to consider though.
The text was updated successfully, but these errors were encountered: