←back to thread

430 points tambourine_man | 1 comments | | HN request time: 0.195s | source
Show context
raverbashing ◴[] No.41878878[source]
Looks like a good design

Doing something like randomly sampling a range of a-zA-Z0-9 and all the symbols without order or structure is absolutely the worse way of doing it for passwords that humans need to type/read, or in fact anything that might get tripped by special characters (like shell scripts, etc)

Yes yes you might lose a bit of entropy, just add one or two characters to it and it will make up for it. Passwords are not so much bruteforced from zero anymore rather than leaked from places with bad password hashes

replies(1): >>41878971 #
tuxone ◴[] No.41878971[source]
I just opened the Password app for the first time to look at the generator. It seems like the pattern is: [a-zA-Z0-9]{6}\-[a-zA-Z0-9]{6}\-[a-zA-Z0-9]{6} with exactly only one uppercase char and one digit. I don't want to do the maths but that looks like a lot of removed entropy.
replies(2): >>41878985 #>>41879126 #
1. nneonneo ◴[] No.41879126[source]
Fully random: 62^18 in that format, or about 107 bits of entropy.

Their approach: ~71 bits per the article (I counted ~73 bits but I’m not using their exact algorithm)

I’d say it’s not too bad. With a good password hashing algorithm you’re looking at nearly 2^100 operations to bruteforce their passwords, which isn’t going to be feasible anytime soon. (Even with a crappy hash algorithm it’s still going to be over 2^80 operations).

And, in this case, that entropy trade off means the passwords are easier to remember and type in, making it more likely for humans to actually use those passwords.