07-05-2016, 03:09 PM
Yes, after I re-read my post it seemed a bit unclear.
Here is a run on a previously cracked hash (WPA). I am in a different directory from where the hashcat binaries (and potfile) are.
So it didn't exit out even though the recovered hash was already in the pot. Furthermore - it wrote the output again (it's now in the pot twice). In a nutshell - 3.00 doesn't seem to read the potfile, yet it writes to it.
Here is a run on a previously cracked hash (WPA). I am in a different directory from where the hashcat binaries (and potfile) are.
Code:
vom@ocl:~/cracking$ cat ../hashcat/hashcat.pot
XXXX:yyyyyyyyyyyy:zzzzzzzzzzzz:AAAAAAAA
vom@ocl:~/cracking$ ../hashcat/hashcat64.bin -a 3 -m 2500 XXXX_yyyyyyyyyyyy.cap.hccap 19?d?d?d?d?d?d
hashcat (v3.00-1-g67a8d97) starting...
OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
- Device #1: Capeverde, 361/659 MB allocatable, 10MCU
- Device #2: Capeverde, 570/992 MB allocatable, 10MCU
- Device #3: AMD FX(tm)-4100 Quad-Core Processor, skipped
Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
* Slow-Hash-SIMD
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c
XXXX:yyyyyyyyyyyy:zzzzzzzzzzzz:AAAAAAAA
Session.Name...: hashcat
Status.........: Cracked
Input.Mode.....: Mask (19?d?d?d?d?d?d) [8]
Hash.Target....: XXXX (yy:yy:yy:yy:yy:yy <-> zz:zz:zz:zz:zz:zz)
Hash.Type......: WPA/WPA2
Time.Started...: Tue Jul 5 08:55:32 2016 (7 secs)
Speed.Dev.#1...: 43394 H/s (11.80ms)
Speed.Dev.#2...: 45059 H/s (11.81ms)
Speed.Dev.#*...: 88453 H/s
Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.......: 601600/1000000 (60.16%)
Rejected.......: 0/601600 (0.00%)
Restore.Point..: 430080/1000000 (43.01%)
Started: Tue Jul 5 08:55:32 2016
Stopped: Tue Jul 5 08:55:42 2016
vom@ocl:~/cracking$ cat ../hashcat/hashcat.pot
XXXX:yyyyyyyyyyyy:zzzzzzzzzzzz:AAAAAAAA
XXXX:yyyyyyyyyyyy:zzzzzzzzzzzz:AAAAAAAASo it didn't exit out even though the recovered hash was already in the pot. Furthermore - it wrote the output again (it's now in the pot twice). In a nutshell - 3.00 doesn't seem to read the potfile, yet it writes to it.