Description
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