Also, thinking about it, it might actually not work exactly like that, since even with --markov-disable oclHashcat changes the left side most frequently e.g.:
531238761
631238761
731238761
831238761
and *not*
531238761
531238762
531238763
531238764
so 531238761 is actually tested much earlier than 53.12% (should be at around 16% already).
But the idea with -s / -l remains the same.
----
That means, to solve your initial problem to start at a certain position, the easiest way is to use a .hcmask file ( https://hashcat.net/wiki/doku.php?id=mas...mask_files ):
e.g. with content:
53?d?d?d?d?d?d?d
456789,5?1?d?d?d?d?d?d?d
6789,?1?d?d?d?d?d?d?d?d
(and with this .hcmask approach you don't even need to use --markov-disable)
Note: one big disadvantage of these reduced keyspaces within the .hcmask file is that full acceleration might not be possible (but might not be that much of a problem at all for a slow algorithm like -m 2500 = WPA/WPA2)
531238761
631238761
731238761
831238761
and *not*
531238761
531238762
531238763
531238764
so 531238761 is actually tested much earlier than 53.12% (should be at around 16% already).
But the idea with -s / -l remains the same.
----
That means, to solve your initial problem to start at a certain position, the easiest way is to use a .hcmask file ( https://hashcat.net/wiki/doku.php?id=mas...mask_files ):
e.g. with content:
53?d?d?d?d?d?d?d
456789,5?1?d?d?d?d?d?d?d
6789,?1?d?d?d?d?d?d?d?d
(and with this .hcmask approach you don't even need to use --markov-disable)
Note: one big disadvantage of these reduced keyspaces within the .hcmask file is that full acceleration might not be possible (but might not be that much of a problem at all for a slow algorithm like -m 2500 = WPA/WPA2)