Hashcat doesn’t write to output file

[theodorebriggs]

Hello,
I am using hashcat to crack a list of md5 hashes and have used the following command

Code:

hashcat -m 0 -a 0 -o out.txt --force hashdump.txt ../rockyou.txt

which gives the output

Code:

Session..........: hashcat
Status...........: Exhausted
Hash.Type........: MD5
Hash.Target......: hashdump.txt
Time.Started.....: Thu Sep 13 01:11:45 2018 (13 secs)
Time.Estimated...: Thu Sep 13 01:11:58 2018 (0 secs)
Guess.Base.......: File (../rockyou.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....:  1459.2 kH/s (0.55ms)
Recovered........: 2/36 (5.56%) Digests, 0/1 (0.00%) Salts
Progress.........: 14344384/14344384 (100.00%)
Rejected.........: 0/14344384 (0.00%)
Restore.Point....: 14344384/14344384 (100.00%)
Candidates.#1....: $HEX[206b6d3831303838] ->
    $HEX[042a0337c2a156616d6f732103]
HWMon.Dev.#1.....: N/A

Started: Thu Oct 13 01:11:45 2024
Stopped: Thu Oct 13 01:11:58 2024

It is clear that 2 of the hashes have been found, however the file out.txt isn't created. Any advice?
Thanks in advance!

[penguinkeeper]

1) Hashcat uses something called a "potfile", which means you only crack new hashes and don't have to keep cracking the same hashes that you have already cracked. To see the 2 recovered, you can either use "--potfile-disable" in your existing command to disable the potfile and re-crack the 2 hashes or "--show" to just get the data from your potfile.

2) You seem to be using an older version, I'm not sure what you're on but updating to 6.2.6 is probably a good idea. It won't solve your issue here, though

[Snoopy]

NEVER use --force

if your hashcat isn't running without, you have some problems with your setup, fix your setup instead of using --force

--force can lead to false positives and other unwanted behavior

~1500 Kh/s per second on MD5? What kind of hardware are you using? even a plain consumer CPU frmo years ago will get you megahashes per second

[theodorebriggs]

Thanks for your answer. I got it.