hashcat Forum
Is there any pass length workaround? - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html)
+--- Forum: General Help (https://hashcat.net/forum/forum-8.html)
+--- Thread: Is there any pass length workaround? (/thread-5324.html)

Is there any pass length workaround? - TheMemelord - 03-14-2016

I know that the password length is 64 characters and that the most consecutive amount of characters is 2, also that the maximum occurrence of a single character is 8 times. I know that in most cases, the highest supported length is 55, but I wanted to at least give it a shot, so I tried the following: 
Code:
mp64.exe -r 8 -q 2 64chars.hcmask | cudaHashcat64.exe -m 1400 -a 3 --separator=: -o out.txt in.txt
and this is the output - 
Code:
cudaHashcat v2.01 starting...

Device #1: GeForce GTX 980, 4096MB, 1367Mhz, 16MCU
Device #1: WARNING! Kernel exec timeout is not disabled, it might cause you erro
rs of code 702
          You can disable it with a regpatch, see here: http://hashcat.net/wiki
/doku.php?id=timeout_patch

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Scalar-Mode
* Raw-Hash
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel ./kernels/4318/m01400_a3.sm_52.64.cubin
Device #1: Kernel ./kernels/4318/markov_be_v1.sm_52.64.cubin


ATTENTION!
 The wordlist or mask you are using is too small.
 Therefore, oclHashcat is unable to utilize the full parallelization power of y
our GPU(s).
 The cracking speed will drop.
 Workaround: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#ho
w_to_create_more_work_for_full_speed


INFO: approaching final keyspace, workload adjusted


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Mask (?1) [1]
Hash.Target....: [hash]...
Hash.Type......: SHA256
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...:        0 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 62/62 (100.00%)
Rejected.......: 0/62 (0.00%)
HWMon.GPU.#1...: 21% Util, 43c Temp,  0rpm Fan


ATTENTION!
 The wordlist or mask you are using is too small.
 Therefore, oclHashcat is unable to utilize the full parallelization power of y
our GPU(s).
 The cracking speed will drop.
 Workaround: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#ho
w_to_create_more_work_for_full_speed


INFO: approaching final keyspace, workload adjusted


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Mask (?1?2) [2]
Hash.Target....: [hash]...
Hash.Type......: SHA256
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...:    16868 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 2232/2232 (100.00%)
Rejected.......: 0/2232 (0.00%)
HWMon.GPU.#1...:  2% Util, 44c Temp,  0rpm Fan


ATTENTION!
 The wordlist or mask you are using is too small.
 Therefore, oclHashcat is unable to utilize the full parallelization power of y
our GPU(s).
 The cracking speed will drop.
 Workaround: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#ho
w_to_create_more_work_for_full_speed


INFO: approaching final keyspace, workload adjusted


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Mask (?1?2?2) [3]
Hash.Target....: [hash]...
Hash.Type......: SHA256
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...:   685.0 kH/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 80352/80352 (100.00%)
Rejected.......: 0/80352 (0.00%)
HWMon.GPU.#1...:  2% Util, 44c Temp,  0rpm Fan


ATTENTION!
 The wordlist or mask you are using is too small.
 Therefore, oclHashcat is unable to utilize the full parallelization power of y
our GPU(s).
 The cracking speed will drop.
 Workaround: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#ho
w_to_create_more_work_for_full_speed


INFO: approaching final keyspace, workload adjusted


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Mask (?1?2?2?2) [4]
Hash.Target....: [hash]...
Hash.Type......: SHA256
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...: 23772.2 kH/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 2892672/2892672 (100.00%)
Rejected.......: 0/2892672 (0.00%)
HWMon.GPU.#1...:  2% Util, 44c Temp,  0rpm Fan


INFO: approaching final keyspace, workload adjusted


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Mask (?1?2?2?2?2) [5]
Hash.Target....: [hash]...
Hash.Type......: SHA256
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...:   500.8 MH/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 104136192/104136192 (100.00%)
Rejected.......: 0/104136192 (0.00%)
HWMon.GPU.#1...: 26% Util, 46c Temp,  0rpm Fan


INFO: approaching final keyspace, workload adjusted


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Mask (?1?2?2?2?2?2) [6]
Hash.Target....: [hash]...
Hash.Type......: SHA256
Time.Started...: Sun Mar 13 19:22:14 2016 (2 secs)
Time.Estimated.: 0 secs
Speed.GPU.#1...:  1371.9 MH/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 3748902912/3748902912 (100.00%)
Rejected.......: 0/3748902912 (0.00%)
HWMon.GPU.#1...: 97% Util, 55c Temp,  0rpm Fan

[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
And then it pretty much stops there. I'm not sure if this is because the keyspace is too large or the length is too large. I understand that I normally would not need to pipe in the output of maskprocessor, rather include the hcmask in the oclhashcat parameters, but I do not believe this way supports the -r and -q parameters, which in this case, are very critical to the vastness of the keyspace. Any help is appreciated! Thanks!

EDIT: I almost forgot, I tried this too - 
Code:
sp64.exe -1 ?l?d --pw-min 64 --pw-max 64 --threshold 2 custom.hcstat ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1 | cudaHashcat64.exe -m 1400 -a 0 --separator=: -o out.txt in.txt
I know that the statsprocessor portion works because I tried outputting a couple of lines and it indeed worked. However, when piped to oclhashcat, the stats output something like this every 10 seconds: 
Code:
Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: [hash]...
Hash.Type......: SHA256
Time.Started...: Sun Mar 13 19:52:45 2016 (30 secs)
Speed.GPU.#1...:        0 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 0
Rejected.......: 0
HWMon.GPU.#1...:  0% Util, 43c Temp,  0rpm Fan
After every 10 seconds, nothing at all changes except for the time in parentheses at the Time.Started line. I'm not sure if this is because the keyspace is too large or it is not doing anything :/

RE: Is there any pass length workaround? - philsmd - 03-14-2016

These questions were already answered in your previous thread https://hashcat.net/forum/thread-5318.html (and you still continue to post the same things, e.g. maskprocessor + hcmask which I told you is not supported).

It doesn't help to open several threads to ask the same questions which were already answered, instead it is against the forum rules.