There were times where I had to rely on password managers too, though. Banking sites are one common place ...
I can't tell you the number of times I've tried to explain to banks that 'security questions' are absolutely worthless, and that their 'secure password' policy is actually worse than no policy at all.
One bank actually requires passwords to be between 6 and 8 characters in length, with at least one letter and one number and no special characters.
What the fuck.
For a pure online bank this would be irresponsible, indeed.
cat /dev/urandom|base64|tr -d '/+'|head -c10
Nearly every site supports a-z,A-Z,0-9 at 10 charactersI think the assumption here is that the password isn't an MD5 hash, but instead something a little more resilient. If it's MD5, you're probably screwed anyway.
This app also uses GPUs to brute force TrueCrypt: http://www.golubev.com/igprs/
See: http://en.wikipedia.org/wiki/Cryptographic_hash_function
Using hash instead of encryption for passwords is major security mistake
zxcvbn assigned my generated password for their site a crack time of ~21 million years.
It offers lots of nice-to-have options.
UTP+NnhabgHKx6
So I make a different password and the sites say it is too weak as it has no special chars or uppercase chars:
5133fe36785a6e01cac7a68c9c111afff5bb4821
So I give up and type Password1 which is normally accepted.