Anyone who would use that tool, would, theoretically, be amazed about the amount of accounts that one could retrieve using this rather dumb method.
Result: there a 3 resulting files (still assuming that the passwd file is named "pFile"):
|pFile.pass||Contains lines with account name, encrypted password and decrypted passwd. U can instantly use this.|
|pFile.done||Contains original lines from pFile; more specifically, those lines which passwords have been cracked.|
|pFile.fail||Contains original lines from pFile; more specifically, those lines which passwords have *not* been cracked.|
The file important for u is "pFile.pass", as it contains the cracked passwords.
Run FastJack on your password file (let it be "pFile" again). Take "pFile.pass" into your collection. throw "pFile.done" away. use a *real* password cracker (like "John The Ripper") on "pFile.fail".
Wakarimashita ka? Jack is only the first wash. Next one. What does FastJack exactly test?
If u want to see more, change the "#undef DEBUG" into a "#define DEBUG" in the FastJack.c file.
Second, the copyleft. This whole here runs under GNU Public License. Basically it means the source is free, as long as u deliver everything derived from it *always* with source and the right to modify.
Third, social. There is always this girl or guy in your neighbourhood, hacking talented but totally "dont-know-how". Help her/him. Makes a better world ;-)
So long, and thanx for the fish!