10-07-2018, 12:57 PM
I cannot reproduce this problem with the same hash mode on hashcat 4.2.1 and combinator attack.
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.
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.