Largest Study of its Kind Shows Outdated Password Practices are Widespread::undefined
The article focuses on password requirements that websites implement, not user behaviors. Common bad practices mentioned:
- Permit very short passwords
- Do not block common passwords
- Use outdated requirements like complex characters
Complex characters are outdated? It also refers to special characters but I guess that’s what I was thinking of. So special characters are in, so what is a complex character then?
Length is the most important thing, everything else is somewhat secondary. We should be shifting thinking of this to passphrases rather than passwords.
I’m sure most of us have seen the “correct horse battery staple” XKCD, but that’s what people really need to think of as passwords now, not my-favourite-celebrity-but-with-the-“e”-changed-to-“3”-and-an-exclamation-mark-at-the-end.
Nah fuck that. Sites need to adopt this passkeys instead. It’s an impossible task for people to have unique credentials for every site, even if they are “memorable”. This is a design issue not a personal responsibility one. When designing for large volumes of people, you have to assume that the majority will do something easy and stupid over difficult and smart.
Thanks for this, I knew the concept but I’ve always had a hard time putting it to words. Yeah, its not like they increase the entropy or anything. Same with diacritics
Reminds me of when Michael tells Dwight he and Jim make different amounts: its not about higher or lower, its just different
I think enforcing complex characters is outdated. Allowing them is enough, since someone brute forcing still needs to consider them. Of course they could try all lower, then mixed, then including complex characters in that order to catch those that don’t. But still, it’s better to have a password made up of compound words that is longer, than S0meth!ngV3ryC0nvolu73D. Or just pure random (aka password generator)
My main issue is places that have a maximum password length. This is firstly a limitation on security, but more importantly throws a red flag because of the potential reasons for having a password length limit!
Depends on the limit really, if the limit is 32 characters or something like that, definite red flag.
If the limit is something like 250 or more characters, I’m more inclined to believe it’s basic protection from all the things that can go wrong when someone repeatedly POSTs whatever the maximum amount of garbage that your server’s request limit allows, at an API that performs cryptographic work.
- Do not block common passwords
Do you mean “not blocking common passwords”?
This implies that I can totally use “password1”