4 ms·
> high entropy passwords You only need that to impose a greater character width against brute force attacks. That is the only value in high entropy. The actua
by austincheney 6y ago
> high entropy passwords
You only need that to impose a greater character width against brute force attacks. That is the only value in high entropy.
The actual reason people think they need this is because it was written into a NIST publication a very long time ago and it just became common practice. As a proof of concept what is the published standard that imposes that practice? I bet you think you need this but cannot find the written standard guidance suggesting it.
The guy who originally wrote that standard later came out and said it was a mistake. Bad advise that he wishes he could take back, but it’s too late everybody thinks they need it and they don’t know why or where that guidance even comes from.
> and it's a PITA to enter in a password field!
Only on a touch screen.
My first example also contains uppercase and punctuation. Think of it like IPv6. When the key space is large enough you don’t need a bunch of bullshit and gimmicks to ensure uniqueness.
- GordonS 6y ago> You only need that to impose a greater character width against brute force attacks. That is the only value in high entropy. That's exactly the reason I meant - to make brute forcing take much longer. > Only on a touch screen Yep, certainly worse on a touch screen, but I hate entering long passwords even on a keyboard - it's OK if it's a field that let's you see what you type, but if it's just asterisks, then I find it hard not seeing that visual feedback.