ERROR: restore value greater keyspace

[skalderis]

Can't restore wpa progress with 1.32. Catalyst 14.9 Win7.64bit. It starts fine from the start (no -s). And everything works fine with 1.31.

Code:

D:\oclHashcat>oclHashcat64.exe -m 2500 -a 3 -w 3 -s 61867462616 e:\test.hccap -1 qwertyupasdfghjklzxcvbnm ?1?1?1?1?1?1?1?1
oclHashcat v1.32 starting...

Device #1: Tahiti, 3072MB, 925Mhz, 32MCU

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel ./kernels/4098/m02500.Tahiti_1573.4_1573.4 (VM).kernel (258840 bytes)
Device #1: Kernel ./kernels/4098/markov_le_v1.Tahiti_1573.4_1573.4 (VM).kernel (35068 bytes)
Device #1: Kernel ./kernels/4098/amp_a3_v1.Tahiti_1573.4_1573.4 (VM).kernel (13624 bytes)

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

ERROR: restore value greater keyspace


D:\oclHashcat>

EDIT: restore value is not greater. 24^8=110075314176

[epixoip]

You are calculating keyspace incorrectly. You're calculating the "real keyspace," and not the "oclHashcat keyspace."

The keyspace value oclHashcat uses is the keyspace of the base loop. The --keyspace switch will calculate this value for you.

With your mask, the base loop keyspace is 7962624, which is far less than 61867462616. This is why oclHashcat tells you the restore value is greater than the keyspace.

Given the real keyspace and the keyspace of the base loop, you should be able to trivially calculate the keyspace of the modifier loop, and then use that value to derive your skip value. I'll leave this as an exercise for the reader.

[skalderis]

Thanks for the reply. My guess it has to do something with last update on "slow hash candidate amplifiers, ported from CPU to GPU". Correct -s is 4475366 Thanks for that!