Hacker News new | past | comments | ask | show | jobs | submit login

I would love to see most drop-in/bolt-on authentication packages (such as DotNet’s Identity system) to adopt “bitwise complexity” as the only rule: not based on length or content, only the mathematical complexity of the bits used. KeePass uses this as an estimate of password “goodness”, and it’s altered my entire view of how appropriate any one password can be.



IIRC the key point there is that it's contextual to whatever generation method scheme you used--or at least what method you told it was used--and it assumes the attacker knows the generation scheme.

So "arugula" will score is very badly in the context of a passphrase of English words, but scores better as a (supposedly) random assortment of lowercase letters, etc.


I'm told that at work we're not allowed to have the same character appear three or more times consecutively in a password (I have never tried).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: