←back to thread

430 points tambourine_man | 1 comments | | HN request time: 0s | source
Show context
eviks ◴[] No.41879128[source]
Why not just use real words with longer password instead? That'd be easier to type than these shorter "word-like" syllables
replies(3): >>41879137 #>>41879148 #>>41879247 #
bombcar ◴[] No.41879137[source]
Even if horse-battery-staple works mathematically people don't trust that it's "really random".

1password supports it as "memorable password".

replies(3): >>41879184 #>>41879233 #>>41879327 #
david422 ◴[] No.41879233[source]
Here's a format I really like:

3CatsHave12Legs!

Easy to memorize, and pretty strong.

replies(4): >>41879283 #>>41879288 #>>41879303 #>>41879414 #
rhaps0dy ◴[] No.41879283[source]
How many more passwords of this format can you construct? `have` is fixed, the `!` at the end is a classic, and the 12 number is pre-determined by true cats and the 3. So the only degrees of freedom you have are:

- the entity number (3)

- the kind of entity (Cats)

- the kind of part (Legs)

and that's not a huge number of combinations.

replies(1): >>41879329 #
bayindirh ◴[] No.41879329[source]
"My4BikesHave9WheelsBecause1IsATricycle?" is a valid one for example?
replies(2): >>41879439 #>>41879624 #
nothercastle ◴[] No.41879439[source]
You have to type that all in without error and the archaic app needs to actually support that many characters
replies(2): >>41879461 #>>41879748 #
1. bayindirh ◴[] No.41879461{3}[source]
I write longer passwords than that periodically. Archaic applications will get shorter variants. No two app will share the same password.

All are no problems for me. With or without a password manager.