05-22-2014, 04:15 PM
oclHashcat 1.20 has some new features to remove hashes if they were already cracked.
For instance, if the hash:plain line is (also) present in the pot file (cudaHashcat.pot in your case), then cudaHashcat won't try to crack that specific hash again and again, therefore it says 1/x recovered (if present in .pot file)...
Another such feature is the so-called outfile remove feature, where hashes can be removed if the identical hashes (w/ corresponding password - plain) is present in the outfile directory (this feature is used heavily in distributed environments) ...
So to see what is happening in you specific case, I would suggest to test:
1. w/o --outfile option
2. backup and remove (or simply move) cudaHashcat.pot, s.t. we are sure that the "potfile remove" feature doesn't trigger in your case
3. test also if the outfile remove feature doesn't trigger
There are also some possibilities to (temporarily) disable those features, e.g w/ --potfile-disable and --outfile-check-timer 0 etc
For instance, if the hash:plain line is (also) present in the pot file (cudaHashcat.pot in your case), then cudaHashcat won't try to crack that specific hash again and again, therefore it says 1/x recovered (if present in .pot file)...
Another such feature is the so-called outfile remove feature, where hashes can be removed if the identical hashes (w/ corresponding password - plain) is present in the outfile directory (this feature is used heavily in distributed environments) ...
So to see what is happening in you specific case, I would suggest to test:
1. w/o --outfile option
2. backup and remove (or simply move) cudaHashcat.pot, s.t. we are sure that the "potfile remove" feature doesn't trigger in your case
3. test also if the outfile remove feature doesn't trigger
There are also some possibilities to (temporarily) disable those features, e.g w/ --potfile-disable and --outfile-check-timer 0 etc