+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: How to interpret hashcat log file to see if an attack was finished? (/thread-13403.html)
How to interpret hashcat log file to see if an attack was finished? - monyanus - 10-07-2025
How can one interpret hashcat's log files to know for certain a attack was finished and not just paused on a checksum? To give an example from one of my log files:
TOP.68db9a07.000a5318 SUB.68db9a83.0002ca64 runtime_start 1759222414
TOP.68db9a07.000a5318 SUB.68db9a83.0002ca64 runtime_stop 1759496840
TOP.68db9a07.000a5318 SUB.68db9a83.0002ca64 hashes->digests_done_new 0
TOP.68db9a07.000a5318 SUB.68db9a83.0002ca64 status-after-work 8
TOP.68db9a07.000a5318 SUB.68db9a83.0002ca64 STOP
TOP.68db9a07.000a5318 proc_start 1759222279
TOP.68db9a07.000a5318 proc_stop 1759496846
TOP.68db9a07.000a5318 STOP
At the end of the file I see stop and number for proc_stop that is similar but not the same as proc_start and the STOP statement. But what does that mean? Does this mean the search spaces has been exhausted and the attack has completed?
What I would have expected in the log is an entry like like "...Finished...", "..Completed...", "...exhausted search space..". In other words a statement that goes beyond the process to state to the user that a given task was finished or completed. To my surprise I could not find any information about interpreting log files either on the forum or in the hashcat wiki.