>randomly generated password doesn't look random enough
>click a few more iterations
>still doesn't look quite good enough
>I'll just make a few improvements and that will be the password
This is the best password protocol. Anyone who suggests otherwise is lying
>>62056573
>this random string isn't random enough
>doesn't look random enough
You dumbass, you're actually making it less "good enough" by making it conform to bias. Random stuff is supposed to have an equal chance of looking "not random enough."
>>62056573
you pretend to do all that to throw off your opponents, but instead use "password"
>>62056591
random password generated is 123456
Ok, this is random so i will keep this password.
>>62056611
Considering how infrequently "try the top 10 most common passwords" is used today in favor of either phishing or brute force, it's probably just as good as anything else. So yeah just go with what the random generator says.
>>62056611
>implying 123456 is not as random as 950843
>>62056638
Actually thinking more about this, I'm also reminded of 2FA and suspicious IP/geolocation alerts. I probably fucking should change all but one of my passwords to 123456 strictly for convenience. No one's going to test them and even if they do I'm going to be asked to authorize their entry.
>>62056591
t.disinfo bot
>>62056590
Generate several short passwords and pick a few of them to combine into one password.
>put 2 unrelated words together and replace two letters with digits
>pretty much immune to dictionary and bruteforce
Why bother doing random ass string again?
>>62056716
https://hashcat.net/wiki/doku.php?id=rule_based_attack
I use a random character generator to generate really long strings, and then just select a handful of characters within the string and copy that for my password
I keep a plain text document with all the names of my sites and passwords on my desktop
how dumb am I
>>62056784
you still need to have an idea of what the rules are
>>62056847
I assumed you were saying leetspeak passwords. The rules are not hard to figure out. o is O, a could be @ or 4, etc
If you're literally talking about random substitution where any given letter could turn into any given integer then that's a bit different, but it's still susceptible to a Markov attack
>>62056822
On your desktop
Have a think about how dumb that is for just a minute
>>62056573
I think I can see a nipple and this is a blue board you sicko