7 ms·
Your blog post says: > "Avoid using simple passwords based on dictionary words" And yet your password algorithm rejects highly secure pass phrases: > "New pa
by Terretta 14y ago
Your blog post says:
> "Avoid using simple passwords based on dictionary words"
And yet your password algorithm rejects highly secure pass phrases:
> "New passwords can contain letters, numbers and punctuation."
Disallowing spaces is particularly annoying for a company with a strong security requirement, as passphrases are simultaneously far more secure and far more memorable than the monkey rules your validation demand.
It gets worse.
If I type a long sentence without spaces such as "thisphraseisdefinitelynotinthedictionary", you give me an orange warning checkmark and suggest:
> "Try using a combination of letters and numbers"
If I replace that long phrase with "abcde1", just 5 lowercase letters and a digit, you give me a green checkmark! Same green checkmark for "abc123", the third most popular password online.
Have whoever wrote your validator needs to go read http://xkcd.com/936/ http://xkcd.com/936/ and really internalize the idea.
EDIT: See also:
1. How people choose passwords: http://www.troyhunt.com/2011/07/science-of-password-selection.html http://www.troyhunt.com/2011/07/science-of-password-selectio...
2. Top 25 passwords: http://www.prweb.com/releases/2012/10/prweb10046001.htm http://www.prweb.com/releases/2012/10/prweb10046001.htm
3. Twitter banned passwords: http://securitywatch.pcmag.com/none/284196-the-twitter-banned-password-list http://securitywatch.pcmag.com/none/284196-the-twitter-banne...
- Niten 14y agoAnyone using this comic to imply that a passphrase is more secure than a short random password hasn't done the math. This is comparing a passphrase drawn from four of the 2048 most common words against not a random password, but one based on a mutated version of one of the 65536 most common words. The example passphrase does have the equivalent of 44 bits of entropy: log_2 (2048^4) = 4 * 11 = 44 However, if we take a random password formed by just seven of the 95 printable ASCII characters, we already have a password four times stronger than such a passphrase: log_2 (95^7) ≈ 45.99 XKCD is great and all, but I wish Randall had been more clear that this comparison does not touch on the strength of a random password, because I have since seen an infuriating number of people point to it to claim that passphrases are more secure than random passwords. They are not.
- pyre 14y agoPassphrases are more secure than random passwords when you factor in the human element. A 64 character passphrase is more memorable than a 64 random character string and less likely to be written on a post-it note.
- apawloski 14y agoBe careful -- you're starting to argue a slightly different point than what your parent made. You're not wrong, but you also haven't done anything to dismiss his claim. He's talking about a 7 character password vs a 4-word passphrase. Not equal sized, 64 character passwords.
- deleted 14y ago[deleted]
- catharsis 14y agoThis assumes that it is known that the password is four random words. The security of this method hinges on the fact that that information is not known.
- miles 14y agoExactly. In a thread about "900gage!@#" being cracked in a few hours[1], this same discussion came up. It's worth reading for those who are wondering about passphrases vs. complex passwords. [1] http://news.ycombinator.com/item?id=4545893 http://news.ycombinator.com/item?id=4545893
- Niten 14y agoThis is, again, not about a random password, as moxie explains in that thread. And as he continues, with regard to the comic: "I think that's totally on the right track, but if people start to do that, chances are that they'll start to create exploitable patterns again". Any password cracker smart enough to exploit the patterns in "900gage!@#" is also smart enough to exploit the construction of an English language passphrase. The passphrase is still secure enough (probably), but it is not more secure than the random password. And if there is any one thing to take away from that thread, it should be that it's foolish to assume the obscurity of your passphrase's formulation gives you any extra security whatsoever.
- fiatpandas 14y ago>Disallowing spaces is particularly annoying for a company with a strong security requirement, as passphrases are simultaneously far more secure and far more memorable than the monkey rules your validation demand. I just don't understand the logic behind some of these password rules. Wouldn't it require more effort to explicitly disallow certain characters? Like, they wrote code somewhere that is specifically making sure your password doesn't have a spaces, and other arbitrarily chosen characters. It doesn't make sense to restrict anything in passwords other than length (and of course testing that is meets certain complexity/length requirements-- smartly). Just set your DB field to be 30 characters, accept any character, and be done with it. There must be some logical explanation behind why companies implement these rules. And banks are the worst. Because people far more experienced than me at programming (e.g. Evernote devs) make these decisions, so there must be some reason. Is the decision a defense against SQL injection techniques? Since injections usually contain spaces. But then again, this is 2013 so you think they would use prepared statements, or something. Madness!
- sdevlin 14y agoSince you're only going to store the hashed value, there's no practical reason to limit the maximum length of the password.
- georgemcbay 14y ago"Since you're only going to store the hashed value"... Look fellas, we've got an optimist over here!
- pyre 14y agoMy understanding is that banks have these weird rules because of the legacy systems that they interface with. I've even heard of new systems built on top of old ones by writing an interface layer on top of the green-screen UI of the old system (i.e. automating the green-screen interaction / screen scraping).
- cynwoody 14y ago
- apawloski 14y agoI don't think UnoriginalGuy actually works for dropbox -- that first line is on the actual blog post too.
- hdra 14y agoseriously though, its 2013, is there any reason to enforce character sets allowed in a password? I should be able to use any kind of character i want.
- j_s 14y agoSee also: Steve Gibson's "Password Haystack" https://www.grc.com/haystack.htm https://www.grc.com/haystack.htm > everyone has always believed or been told that passwords > derived their strength from having “high entropy”. [...] > But [...] when the only available attack is guessing, > that long-standing common wisdom is not correct! (Practical advice for normal users seems to be Steve's raison d'etre; I would be glad to hear anyone share their concerns about his recommendations.)