+- 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: attack mode 1 and session restore? (/thread-7857.html)
attack mode 1 and session restore? - Wirl - 10-05-2018
Hello!
Is there some technical reason or just a bug that prevents me from doing a --session blaha --restore when I created the session with -a 1?
Currently combining the current dictionary and when using --session blaha --restore, it starts all over again.
This is how I ran hashcat: hashcat64.exe -m 2500 -a 1 --session blaha X:\blaha.hccapx X:\wordlist.txt X:\wordlist.txt
RE: attack mode 1 and session restore? - undeath - 10-05-2018
maybe you haven't reached a checkpoint yet? How far was the attack?
RE: attack mode 1 and session restore? - Wirl - 10-06-2018
I don't remember the exact numbers right now but the whole session would have taken a bit over two days to run and I had less than 12 hours left when I cancelled it. If I don't use the combinator attack, I can quit and resume sessions without problems though.
RE: attack mode 1 and session restore? - undeath - 10-07-2018
I cannot reproduce this problem with the same hash mode on hashcat 4.2.1 and combinator attack.
Code:
$ hashcat64.bin -m2500 --session test /tmp/test.hccapx wordlists/1 wordlists/2 -a1
Session..........: test
Status...........: Quit
Hash.Type........: WPA-EAPOL-PBKDF2
Progress.........: 12518908/15000424 (83.46%)
Restore.Point....: 327680/394748 (83.01%)
$ hashcat64.bin --session test --restore
Session..........: test
Status...........: Running
Hash.Type........: WPA-EAPOL-PBKDF2
Progress.........: 12518908/15000424 (83.46%)
Restore.Point....: 327680/394748 (83.01%)I guess hashcat just hadn't reached a restore point yet. Especially with combinaor attack this can take some time. The restore point you see above at 83% was the first and only one I saw in my testing session.
RE: attack mode 1 and session restore? - Wirl - 10-07-2018
Hm!
Interesting.
The Restore.Point is always at 0% for me, even when not using the combinator attack but --restore works anyway.
Using hashcat 4.2.1 (x64) in Windows if that can narrow down the problem.