Restore File Questions

[NeonFlash]

hi,

I have a few questions about the recent feature added in oclHashcat-plus, the restore session feature.

1. If I start an attack with a session name "MD5" like this:

oclhashcat-plus32.exe -m 0 -n 400 --session=MD5 -a 0 md5.txt dict.txt

then I abort the attack by pressing "q".

all the details related to the status are stored in the restore file.

2. now, I delete the existing md5.txt file and replace it with a new one, which has fewer hashes than the original one. lets say, original file initially had 100 hashes, in previous session, 20 got cracked. so 80 remaining.

now, I replace it with a file containing 60 hashes.

if I restore the session now:

oclhashcat-plus32.exe --restore --session=MD5

will the restore still work?

will it resume the attack from the previous wordlist position where it left and continue or again start from the beginning of the hash list?

[mastercracker]

hi,

I have a few questions about the recent feature added in oclHashcat-plus, the restore session feature.

1. If I start an attack with a session name "MD5" like this:

oclhashcat-plus32.exe -m 0 -n 400 --session=MD5 -a 0 md5.txt dict.txt

then I abort the attack by pressing "q".

all the details related to the status are stored in the restore file.

2. now, I delete the existing md5.txt file and replace it with a new one, which has fewer hashes than the original one. lets say, original file initially had 100 hashes, in previous session, 20 got cracked. so 80 remaining.

now, I replace it with a file containing 60 hashes.

if I restore the session now:

oclhashcat-plus32.exe --restore --session=MD5

will the restore still work?

will it resume the attack from the previous wordlist position where it left and continue or again start from the beginning of the hash list?

For sure, it does not "start from the beginning of the hash list" since all the hashes are loaded every time but it's still a good a question. I doubt that the hash list would be saved with the restore file so it will probably continue from where you stopped the attack with the new hash list. Just try it, if it says 80 hashes loaded then I am wrong. If it says 60 hashes loaded then I am right.

[M@LIK]

Since you both are too lazy to try, or maybe busy like a bee, I made a quick test and results are:

Code:

ERROR: Loaded digests from hashlist is async to data in restore file

However, it's only checking for the number of hashes and not the hashes themselves.

[atom]

It stores which hash was already cracked (per position). Thats why you can not modify the hashlist afterwards or the restore will not work.

[splash_]

What could be the issue when the restored session gets stuck (no progress is seen) + progress % jumps to roof?

$ rm testing_session.restore
$ oclHashcat-plus-0.14/oclHashcat-plus64.bin -m 3100 --gpu-loop=1000 --gpu-accel=800 -a 3 hashes/hashes.txt -1 ?l --session=testing_session ?1?1?1?1?1?1

...

[s]tatus [p]ause [r]esume [b]ypass [q]uit => q

Session.Name...: testing_session
Status.........: Aborted
Input.Mode.....: Mask (?1?1?1?1?1?1)
Hash.Target....: File (hashes/hashes.txt)
Hash.Type......: Oracle 7-10g
Time.Started...: Sun Apr 14 15:44:34 2013 (17 secs)
Time.Estimated.: Sun Apr 14 15:54:48 2013 (9 mins, 56 secs)
Speed.GPU.#1...: 132.9k/s
Speed.GPU.#2...: 129.0k/s
Speed.GPU.#3...: 127.4k/s
Speed.GPU.#4...: 125.0k/s
Speed.GPU.#*...: 514.3k/s
Recovered......: 0/2598 (0.00%) Digests, 0/2598 (0.00%) Salts
Progress.......: 22461284352/802563186048 (2.80%)
Rejected.......: 0/22461284352 (0.00%)
HWMon.GPU.#1...: 95% Util, 63c Temp, 10% Fan
HWMon.GPU.#2...: 96% Util, 66c Temp, 10% Fan
HWMon.GPU.#3...: 96% Util, 59c Temp, 10% Fan
HWMon.GPU.#4...: 94% Util, 52c Temp, 10% Fan

Started: Sun Apr 14 15:44:34 2013
Stopped: Sun Apr 14 15:44:52 2013

AFAIK, restored session should pick up on 2.80%, right? The behavior I see is this one:

$ oclHashcat-plus-0.14/oclHashcat-plus64.bin --restore --session=testing_session

[s]tatus [p]ause [r]esume [b]ypass [q]uit => s
Session.Name...: testing_session
Status.........: Running
Input.Mode.....: Mask (?1?1?1?1?1?1)
Hash.Target....: File (hashes/hashes.txt)
Hash.Type......: Oracle 7-10g
Time.Started...: Sun Apr 14 15:45:36 2013 (23 secs)
Time.Estimated.: Sun Apr 14 15:46:02 2013 (19 secs)
Speed.GPU.#1...: 132.6k/s
Speed.GPU.#2...: 128.9k/s
Speed.GPU.#3...: 127.4k/s
Speed.GPU.#4...: 124.3k/s
Speed.GPU.#*...: 513.2k/s
Recovered......: 0/2598 (0.00%) Digests, 0/2598 (0.00%) Salts
Progress.......: 431615508480/802563186048 (53.78%)
Rejected.......: 0/431615508480 (0.00%)
HWMon.GPU.#1...: 64% Util, 64c Temp, 10% Fan
HWMon.GPU.#2...: 64% Util, 67c Temp, 10% Fan
HWMon.GPU.#3...: 88% Util, 59c Temp, 10% Fan
HWMon.GPU.#4...: 89% Util, 52c Temp, 10% Fan

[s]tatus [p]ause [r]esume [b]ypass [q]uit => s
Session.Name...: testing_session
Status.........: Running
Input.Mode.....: Mask (?1?1?1?1?1?1)
Hash.Target....: File (hashes/hashes.txt)
Hash.Type......: Oracle 7-10g
Time.Started...: Sun Apr 14 15:45:36 2013 (40 secs)
Time.Estimated.: Sun Apr 14 15:46:35 2013 (34 secs)
Speed.GPU.#1...: 132.5k/s
Speed.GPU.#2...: 128.9k/s
Speed.GPU.#3...: 127.4k/s
Speed.GPU.#4...: 124.3k/s
Speed.GPU.#*...: 513.1k/s
Recovered......: 0/2598 (0.00%) Digests, 0/2598 (0.00%) Salts
Progress.......: 431615508480/802563186048 (53.78%)
Rejected.......: 0/431615508480 (0.00%)
HWMon.GPU.#1...: 97% Util, 70c Temp, 10% Fan
HWMon.GPU.#2...: 96% Util, 72c Temp, 10% Fan
HWMon.GPU.#3...: 96% Util, 64c Temp, 10% Fan
HWMon.GPU.#4...: 94% Util, 57c Temp, 10% Fan

[s]tatus [p]ause [r]esume [b]ypass [q]uit => q

Session.Name...: testing_session
Status.........: Aborted
Input.Mode.....: Mask (?1?1?1?1?1?1)
Hash.Target....: File (hashes/hashes.txt)
Hash.Type......: Oracle 7-10g
Time.Started...: Sun Apr 14 15:45:36 2013 (47 secs)
Time.Estimated.: Sun Apr 14 15:46:47 2013 (40 secs)
Speed.GPU.#1...: 132.5k/s
Speed.GPU.#2...: 128.9k/s
Speed.GPU.#3...: 127.4k/s
Speed.GPU.#4...: 124.3k/s
Speed.GPU.#*...: 513.1k/s
Recovered......: 0/2598 (0.00%) Digests, 0/2598 (0.00%) Salts
Progress.......: 431615508480/802563186048 (53.78%)
Rejected.......: 0/431615508480 (0.00%)
HWMon.GPU.#1...: 88% Util, 70c Temp, 10% Fan
HWMon.GPU.#2...: 86% Util, 71c Temp, 10% Fan
HWMon.GPU.#3...: 87% Util, 65c Temp, 10% Fan
HWMon.GPU.#4...: 83% Util, 57c Temp, 10% Fan

I ran it again with ?l?d?s?u saving the session on testing_session2 and it also got stuck/progress jumped (it jumped from 0.02% - before quit - to 21.68% - even though the absolute number is the same).

NOTE: for this post I did a quick check, but I already left the restored session running for some 10min - no luck there too. Stuck on 431615508480.

[Rolf]

partially known bug, reported on trac.