06-30-2014, 06:25 PM
Not sure if a bug or whether the .new file is used as a temp file.
Observed with the latest beta 1.30b23 and previous versions.
Noticeable when cracking large hashlists eg 1GB plus. After the cracking process has finished (during the time when oclhashcat is unresponsive to commands) a .new (hashes) file is generated, it is then deleted and regenerated again. Not sure if the part where is is deleted and generated again normal.
Observed with the latest beta 1.30b23 and previous versions.
Noticeable when cracking large hashlists eg 1GB plus. After the cracking process has finished (during the time when oclhashcat is unresponsive to commands) a .new (hashes) file is generated, it is then deleted and regenerated again. Not sure if the part where is is deleted and generated again normal.