3 ms·
I used to do something very similar to this, for around 5 years. It works fairly well, but I've moved away from it largely because: There are always exceptions
by linsomniac 9y ago
I used to do something very similar to this, for around 5 years. It works fairly well, but I've moved away from it largely because: There are always exceptions that won't work (you can't have one scheme that both satisfies "you must have one special character" and "you cannot have any special characters"), and it also doesn't let you change your password for a site. I was able to come up with something that worked in 95% of the cases, it was the 5% that got me to stop using it.
- z1mm32m4n 9y agoThat's what the incrementing variable is for. Of course, you have to then remember how many times you've changed your password for any given site.
- rosser 9y agoHow does incrementing a counter address some sites requiring special characters while others reject them?
- dheera 9y agoThe counter only addresses requirements to change password periodically. The special character requirement is addressed by tacking on 'Aa$1' to all passwords (they asked for it; it's what I tacked to all the (good) passwords I memorized even before I had this method).
- wodenokoto 9y agoAll your passwords have special characters. Some places do not accept special characters in passwords. This is what your scheme doesn't address.
- amorphid 9y agoThat works until you visit the website for my insurance company... "You must use one of these special characters: %^&*()"