3 ms·
Some DBMS' do require a limit... eventually. I think 256 is a reasonable bound, since that allows very generous pass phrases. And actually, the NIST password r
by vorpalhex 9y ago
Some DBMS' do require a limit... eventually. I think 256 is a reasonable bound, since that allows very generous pass phrases.
And actually, the NIST password recommendations are very reasonable, at least currently.
- nokcha 9y agoBut you shouldn't be storing a raw, unhashed password in the database anyway.
- Someone1234 9y agoThe current NIST requirements almost read like someone at NIST read the famous XKCD[0] and decided to implement it. Likely the best standard we've ever had in its reasonableness. [0] https://xkcd.com/936/ https://xkcd.com/936/
- maxk42 9y agoYou failed the test. Back to Security 101 with you! The point being made is that all passwords should be hashed and a hash is going to be fixed-length. Therefore there should be no limit on password length beyond, say the limit of the total HTTP POST size -- but you're not using a megabyte-long password, are you?
- GauntletWizard 9y agoI use The Complete Works of William Shakespeare, Unabridged as my password to several sites. How could you get more secure?
- 0xfeba 9y agoUnix or windows line endings?
- Sohcahtoa82 9y agoI mix them up using a CSPRNG to flip a coin.
- amw 9y agoI replace all line-endings with "Bee Movie" as binary in avi format.
- Sohcahtoa82 9y agoAnd every time someone says "Bee", it's replaced with "We Are Number One"
- lmm 9y agoWhat meaningful distinction are you drawing between a 1mb limit and a 256 character limit?
- deleted 9y ago[deleted]
- sli 9y agoThey aren't. They're just referring the the POST request size limit (which isn't hard set at one megabyte, but that's not their point, either).
- layoric 9y agoOnly the hash should be stored so limit of the original password is mute
- excitom 9y agoPedantic comment: The word is "moot"