-
-
Notifications
You must be signed in to change notification settings - Fork 296
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
We did pcpartpicker.com dirty #518
Comments
|
Thank you for the thoughtful comment!
That's my understanding as well, but to be sure I checked on the latest NIST guidelines:
You also wrote:
I agree with this also, and so it seems we both concur with NIST's guidelines. However, I feel the linked Appendix A is as close to a perfect statement of what's wrong with the world that dumbpasswordrules.com is aiming to call out. That is, in a misguided attempt to help users choose better passwords, many websites add onerous "complexity" requirements that bother users and don't improve security for anybody. Worse, these complexity rules inhibit users from following best practices as recommended by NIST -- in particular, using a cryptographically secure password generator, which can create high-entropy passwords that nonetheless don't meet the complexity requirements of a specific site. With that in mind, a low-risk site like pcpartpicker having somewhat inadequate requirements isn't ideal, but in my opinion it is easily preferable, and so it feels out of place on the site. That's just my $.02. :) |
We complain that pcpartpicker doesn't have any dumb rules?
Okay I guess that's dumb, but it's not a password rule.
The text was updated successfully, but these errors were encountered: