Actually yes there is.
The only thing you need to make sure is that markov is *disabled*, otherwise you can't easily say at which percentage that number is being checked (that also means that if you had to run all values up to 531238761 too, markov had to be disabled for that range/run too).
Calculate the percentage:
531238761 / 10^9 = 531238761 / 1000000000 = 0.531238761
(53.12%)
Important, get the value for the whole "keyspace":
Do some more math to get the -s value:
(total keyspace * percentage = -s value)
100000000 * 0.531238761 = 53123876
Run it:
Note: you must use --markov-disable (otherwise this -s value is not correct)
Note2: I always recommend that you choose the -s value a little bit lower than the calculated one (just to be very sure that we actually don't skip anything, so maybe choose a -s value around 53000000 or so. if you are concerned enough to miss anything
)
The only thing you need to make sure is that markov is *disabled*, otherwise you can't easily say at which percentage that number is being checked (that also means that if you had to run all values up to 531238761 too, markov had to be disabled for that range/run too).
Calculate the percentage:
531238761 / 10^9 = 531238761 / 1000000000 = 0.531238761
(53.12%)
Important, get the value for the whole "keyspace":
Code:
$ ./oclHashcat64.bin -m 2500 -a 3 --keyspace hashcat.hccap ?d?d?d?d?d?d?d?d?d
100000000Do some more math to get the -s value:
(total keyspace * percentage = -s value)
100000000 * 0.531238761 = 53123876
Run it:
Code:
./oclHashcat64.bin -m 2500 -a 3 -s 53123876 --markov-disable hashcat.hccap ?d?d?d?d?d?d?d?d?dNote: you must use --markov-disable (otherwise this -s value is not correct)
Note2: I always recommend that you choose the -s value a little bit lower than the calculated one (just to be very sure that we actually don't skip anything, so maybe choose a -s value around 53000000 or so. if you are concerned enough to miss anything
)