Cracked hashes not recognized across multiple jobs #126
Comments
|
When you enter enter hashes, hashes that have been already cracked will display a yellow exclamation (see picture). Do you see that exclamation mark? It's not perfect, but you can then go to Library -> Hash Cache to see all cracked hashes and their passwords. The situation will improve somewhat with the next release with the introduction of "hash lists", which allow to share one list of hashes across multiple jobs. So if two jobs are working on one hash list then either job will see the work—the cracked hashes—of the other. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
I’m experiencing an issue where Fitcrack doesn’t recognize previously cracked hashes across different jobs.
Steps to Reproduce:
1. Create a job using a dictionary attack, which successfully cracks some hashes.
2. Create a second job using a mask attack on the same set of hashes.
3. Observe that the second job attempts to crack hashes that were already cracked in the first job. 
Expected Behavior:
Fitcrack should recognize hashes that have already been cracked in previous jobs and avoid reprocessing them.
Proposed Solution:
Implement a shared potfile mechanism across all jobs, or provide an option to specify a common potfile path in the configuration. This would allow Fitcrack to track cracked hashes globally and prevent redundant processing or identify the cracked hashes in the database
The text was updated successfully, but these errors were encountered: