Man, I seriously underestimated the power of GPU password crackers!
I had an 11-character password which I thought was pretty good--b1Ackb0x3!1, and that was cracked. I'm pretty sure I didn't succumb to any phishing attempts.
Good thing I use 20+ characters for passphrases.
I had an 11-character password which I thought was pretty good--b1Ackb0x3!1, and that was cracked. I'm pretty sure I didn't succumb to any phishing attempts.
Good thing I use 20+ characters for passphrases.
leetspeak is no good.
EDIT:
My password was also weak, but fortunately it wasn't cracked yet. (I would like to tell you what the password is like, but maybe I should not give hints.)
the password above is not exactly l33tsp34k as i know it and if i had to configure a password cracker
config file to attempt leetspeak cracking styles... i would not have guessed to match his style up.
it seems someone actually ran a gpu(s) password cracker for days on end.. if i had to guess.
i wonder what the time line is for that file being first noticed versus the file being in the wild for
anyone to get? Two weeks? 5 days? hmm
You don't even need a dictionary, all you need is a histogram to dramatically reduce the search space. That is why random is the only way to go.
You are right. That would be an excellent method to reduce the amount of work. But random may not really
help unless it is spitting out some very very odd characters people normally never use and probably do not
even know how to type in the USA. Do they output characters like this? (which i found on a webpage about
a histogram of a rainbow table website).
2 times the character
2 times the character ®
2 times the character ¯
2 times the character »
2 times the character Ø