Rules attack - restore not working
#1
Hello , strange things. 
I use rule attack, but restore point always  on 0%. Even if i press C - nothing happens.
Tried with --restore-file-path=x.restore 
Also no result. 
This is bug ?
Reply
#2
which algorithm? command line?
Reply
#3
./hashcat -a 0 -m 21800 hasht.txt rockyou.txt -r /rules/RuleMy.rule --session s1 -d 8,9,10,11,12,13,14 --restore-file-path=x.restore
Reply
#4
just explain what you see and experience.

Do you mean that it takes a while until the next restore point is reached ?
Maybe it's only a matter of having a little bit of patience until the current work is done and the next restore point is reached ?
Reply
#5
(04-18-2020, 09:30 AM)philsmd Wrote: just explain what you see and experience.

Do you mean that it takes a while until the next restore point is reached ?
Maybe it's only a matter of having a little bit of patience until the current work is done and the next restore point is reached ?

It worked 3days on keyspace = 745836246080 and 30% was done, after that was very hot day and i understood that hashcat will abort brute because of overheating of one gpu. I look at checkpoint and it was 0%. Then i press C key to make manual checkpoint but nothing happend. Ofcource after abort i tried to restore and it started from the beggining.

Now i start this again. Pressed C

Code:
....
Progress.........: 944111616/745836246080 (0.13%)
Rejected.........: 0/944111616 (0.00%)
Restore.Point....: 0/14344384 (0.00%)
.....

Checkpoint enabled. Will quit at next restore-point update.




After some time it stopped. And when i restore it began from start.
And can i change VALUE of Restore.Point?
Reply
#6
The status at the end must be
Code:
Status...........: Aborted (Checkpoint)

The value of the Restore.Point must be increased (greater than 0)... Attention: the progress line is not the correct one, it's something different:
Code:
Restore.Point....: 3586096/14344384 (25.00%)

The exit code (see docs/status_code.txt) must be 3
Code:
echo $?
3

(on windows the exit code might be checked by something like: echo %ERRORLEVEL%)

if the restore.point increased the hashcat.restore file will have the updated value and --restore will use this new checkpoint
Reply
#7
I guess i have problems with restore when i using rockyou with 50k+  rules file
I tried to split rockyou on 10 parts but Restore.Point doesn't wont to work


Quote:Recovered........: 0/1 (0.00%) Digests
Progress.........: 20919998678/51995000000 (40.23%)
Rejected.........: 0/20919998678 (0.00%)
Restore.Point....: 0/1000000 (0.00%)

(ubuntu + last hashcat from git)
Reply
#8
My guess is that with that many rules, the workload profile (-w 2 ? or -w 3) and the amount of GPUs, it might just take a lot of time to reach the next checkpoint.
With -w 1 more checkpoints will be reached faster, but that of course is not good for the hash rate.

I guess there is little you can do here, besides having some patience.
Reply
#9
-w 3 and 7 gpu.
Ok, thanks for answer.I Will use splitted to many small files wordlist to prevent loss of huge progress
Reply