I want to produce reports of crackable passwords which do not actually contain the plaintext password itself. How do I do this?
This is easily achieved by tweaking the “Reporter” script in Crack5.0; a little examination of the code, and it should be obvious what to do. • I want to compose my own rulesets; where can I find documentation? Documentation on the rulesets is a bit scanty, but this file should be of help. • I want to use Crack to check users’ passwords when they are changing them; can I do this? Yes, however you ought to be looking at my CrackLib software which does this, and not Crack itself. • Crack 4.x used to have this really neat feature where it would store passwords that it had not managed to guess, and it would not bother to attack them again next time. Why doesn’t 5.x do this? I want this functionality back! I removed this functionality because many Crack users were not bothering to clear out the history of so-called “unguessable” passwords every few months; the point was that a password that was unguessable one month, might become guessable the next month, when other updates/additions might
Related Questions
- I want to produce reports of crackable passwords which do not actually contain the plaintext password itself. How do I do this?
- My online bank forces me to change my password every month. Can PasswordMaker generate different passwords for the same site?
- Do ChexSystems reports contain any positive information?
