Bottleneck, and my 31 character limit. Ideas?

[InfDoleo]

I have a hash I want to work with, and it is 13 numbers, 0-12, in random order, non-repeating, separated by hyphens, and enclosed on either side by braces.

For example:
[5-10-3-0-2-7-11-9-6-8-1-12-4]

I have already dumped all 6.2 billion combinations to a series of text files via a PHP script. After reading oclHashcat documentation today, I see it can do permutations, and it can do mask attacks. Can they be combined? An internal perm/mask attack would be worlds faster than reading in 166 GIGABYTES of text files. I cant imagine I'd get any GPU efficiency that way.

Is that type of attack possible?

[atom]

That's an interessting question. Thing is, we dropped native permutation attack from oclHashcat a while back. But even then it was not really an option becuase there was no way to add a separator character like you would need.

But then, you don't really need to write the 166gb to file. You can simply pipe the output from your scripts (make them print to stdout) and oclHashcat can read it from stdin. That is of course slower than a native kernel doing it, but if the hash youwant to crack is a slow one that doesnt matter anyway.

But then, if your hash is a fast one you can simply mask attack this thing. It would be so fast that you can simply ignore the permutation effect, check the invalid but therefore you get the full gpu acceleration.

[InfDoleo]

A mask attack wouldn't be any faster - with 13 permutations thats a total # of possible passwords of 6.2 billion.

If I mask it, I'd have to do something like:
x=0 or 1
y=0-9
[xy|xy|xy...]

Unless it supports x=0-12. But even if it does:

Thats 12 numbers, with a keyspace of 12. 12x12x12x12x12x12x12x12x12x12x12x12=8916100448256

Given there are 13 of them, thats over 1400x more guesses.

So, yeah, gotta stick with my bigass datafile

That being said, now it's not cracking anything over 34 characters. Ugh.

[InfDoleo]

I deleted my original post after finding the wiki page that details the 31 character limit, but decided to repost it... it's between the dashed lines. But I have other questions/issues...

-------------------
I'm doing testing now that I got my GPU's working, and it won't crack a password. I know it's in there as I SHA1'ed the password myself and pasted it in the command line.

When I SHORTEN the password, it works.

When i crack this: 903b8b9cbd54b01dce32d0038821a7725c97806a
Which is: 8|7|9|4|2|10|6|11|12|1|0|5|13|3|14

It does not find it.

When I crack: 4845d07488575413261631f67d57e5678c5ccc8b
Which is: 8|7|9|4|2|10|6|11|12|1|0|5|13|3|1

It finds it. It finds a length 33, fails on 34. Huh?

Now I know old versions of oclhashcat had a limit of 15, but nowhere am I seeing a limit of less than 55 (found that googling somewhere).

Anyone have any idea?
---------------

So, like I said, I found the page that says it can crack a 55 character password, but, it has to be in 2 parts, and each part cant be over 31 characters. That SUCKS. I actually bought $800 in hardware today for this project I'm working on, only to find out I can't do it because of that odd restriction? To top it off - closed source - I can't just change the code (32 characters sure sounds like a bit-related limit to me).

I cant even use the combiner - I'm working with a permutation of numbers. I may have to try it with a special set of masks. Which will VAAAASTLY increase the cracking time. 13 numbers, 0-12, no repeats:

Using my permutated list:
13x12x11x10x9x8x7x6x5x4x3x2x1=6,227,020,800 possible options

Using the masks, assuming I can set a 0-12 range on a single 'character':
13x13x13x13x13x13x13x13x13x13x13x13x13=302,875,106,592,253 hashes

Forty eight THOUSAND times the work.

And this list of 13 numbers is a preliminary test, I was hoping to work with numbers up to 18 (which is absurdly high, but still reasonable if it's a permutation).

Is there ANY way to do this, or am I screwed by a programming limitation?

Can anyone think of a fancy way to make it work? I briefly thought of tables where it was split in half, but that multiples the work many times over as well.

Ugh

[undeath]

did not read properly. meh.

[Xanadrel]

I will just reply to this :

To top it off - closed source - I can't just change the code (32 characters sure sounds like a bit-related limit to me).

topkek, that's all.

[InfDoleo]

I will just reply to this :

To top it off - closed source - I can't just change the code (32 characters sure sounds like a bit-related limit to me).

topkek, that's all.

Even after googling topkek, still not sure what you mean by that.

[atom]

Well if you stick to mask-attack the maximum is 55, so I really think you want to do that

[atom]

If you use -a 3 (mask-attack) it will work because the limit with mask attack is 55.

root@et:~/oclHashcat-1.36# ./oclHashcat64.bin -m 100 hash '8|7|9|4|2|10|6|11|12|1|0|5|13|3|14' -a 3 -w 3 --potfile-disable
oclHashcat v1.36 starting...

Device #1: Tahiti, 2981MB, 1000Mhz, 32MCU
Device #2: Tahiti, 2981MB, 1000Mhz, 32MCU
Device #3: Tahiti, 2981MB, 1000Mhz, 32MCU

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/4098/m00100_a3.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (227716 bytes)
Device #1: Kernel ./kernels/4098/markov_be_v1.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (35108 bytes)
Device #2: Kernel ./kernels/4098/m00100_a3.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (227716 bytes)
Device #2: Kernel ./kernels/4098/markov_be_v1.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (35108 bytes)
Device #3: Kernel ./kernels/4098/m00100_a3.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (227716 bytes)
Device #3: Kernel ./kernels/4098/markov_be_v1.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (35108 bytes)


ATTENTION!
The wordlist or mask you are using is too small.
Therefore, oclHashcat is unable to utilize the full parallelization power of your GPU(s).
The cracking speed will drop.
Workaround: https://hashcat.net/forum/thread-4161.html


INFO: approaching final keyspace, workload adjusted

903b8b9cbd54b01dce32d0038821a7725c97806a:8|7|9|4|2|10|6|11|12|1|0|5|13|3|14

Session.Name...: oclHashcat
Status.........: Cracked
Input.Mode.....: Mask (8|7|9|4|2|10|6|11|12|1|0|5|13|3|14) [34]
Hash.Target....: 903b8b9cbd54b01dce32d0038821a7725c97806a
Hash.Type......: SHA1
Time.Started...: 0 secs
Speed.GPU.#1...: 0 H/s
Speed.GPU.#2...: 0 H/s
Speed.GPU.#3...: 0 H/s
Speed.GPU.#*...: 0 H/s
Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.......: 1/1 (100.00%)
Skipped........: 0/1 (0.00%)
Rejected.......: 0/1 (0.00%)
HWMon.GPU.#1...: 89% Util, 49c Temp, 51% Fan
HWMon.GPU.#2...: 89% Util, 52c Temp, 57% Fan
HWMon.GPU.#3...: 90% Util, 51c Temp, 55% Fan

Started: Sun Apr 5 23:37:47 2015
Stopped: Sun Apr 5 23:37:49 2015

[InfDoleo]

Right, but to use that mask, I have to check 302 trillion possible outcomes, where as with the list I check against 6 billion, because there are no repeats of any numbers. Additionally, it doesnt appear that I can put '12' as a single 'character' so I'd have to use a charset that was like ?1?d|?1?d|?1?d where -1 was 0 and 1. So now instead of 13 spots of 13 different numbers (13^13) now it's 20^20.

I've been looking all afternoon - if there is some way to force oclhc to use more-than-1-character strings as characters (where ?1 could be 0-12), or a way to make sure values aren't re-used, then I'd love to go that way. As it stands now, I cannot.

And as for just using -3 with my file as is - it treats each line as a mask and applies it, so instead of one status screen at the end, I get one for EACH line... like so:

Session.Name...: oclHashcat
Status.........: Running
Input.Mode.....: Mask (7|8|9|3|10|6|2|1|11|12|0|4|5) [37] (0.00%)
Hash.Target....: 74e73c5d84a25af75ecf52c10426566a787e7ac2
Hash.Type......: SHA1
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...: 0 H/s
Speed.GPU.#2...: 0 H/s
Speed.GPU.#3...: 0 H/s
Speed.GPU.#*...: 0 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 1/1 (100.00%)
Skipped........: 0/1 (0.00%)
Rejected.......: 0/1 (0.00%)
HWMon.GPU.#1...: 0% Util, 36c Temp, 33% Fan
HWMon.GPU.#2...: 0% Util, 40c Temp, 20% Fan
HWMon.GPU.#3...: 68% Util, 32c Temp, 20% Fan


ATTENTION!
The wordlist or mask you are using is too small.
Therefore, oclHashcat is unable to utilize the full parallelization power of your GPU(s).
The cracking speed will drop.
Workaround: https://hashcat.net/forum/thread-4161.html


INFO: approaching final keyspace, workload adjusted


Session.Name...: oclHashcat
Status.........: Running
Input.Mode.....: Mask (7|8|9|3|10|6|2|1|11|12|4|0|5) [37] (0.00%)
Hash.Target....: 74e73c5d84a25af75ecf52c10426566a787e7ac2
Hash.Type......: SHA1
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...: 0 H/s
Speed.GPU.#2...: 0 H/s
Speed.GPU.#3...: 0 H/s
Speed.GPU.#*...: 0 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 1/1 (100.00%)
Skipped........: 0/1 (0.00%)
Rejected.......: 0/1 (0.00%)
HWMon.GPU.#1...: 0% Util, 36c Temp, 33% Fan
HWMon.GPU.#2...: 0% Util, 40c Temp, 20% Fan
HWMon.GPU.#3...: 56% Util, 32c Temp, 20% Fan


ATTENTION!
The wordlist or mask you are using is too small.
Therefore, oclHashcat is unable to utilize the full parallelization power of your GPU(s).
The cracking speed will drop.
Workaround: https://hashcat.net/forum/thread-4161.html


INFO: approaching final keyspace, workload adjusted


Session.Name...: oclHashcat
Status.........: Running
Input.Mode.....: Mask (7|8|9|3|10|6|2|1|11|12|4|5|0) [37] (0.00%)
Hash.Target....: 74e73c5d84a25af75ecf52c10426566a787e7ac2
Hash.Type......: SHA1
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...: 0 H/s
Speed.GPU.#2...: 0 H/s
Speed.GPU.#3...: 0 H/s
Speed.GPU.#*...: 0 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 1/1 (100.00%)
Skipped........: 0/1 (0.00%)
Rejected.......: 0/1 (0.00%)
HWMon.GPU.#1...: 0% Util, 36c Temp, 33% Fan
HWMon.GPU.#2...: 0% Util, 40c Temp, 20% Fan
HWMon.GPU.#3...: 57% Util, 32c Temp, 20% Fan


ATTENTION!
The wordlist or mask you are using is too small.
Therefore, oclHashcat is unable to utilize the full parallelization power of your GPU(s).
The cracking speed will drop.
Workaround: https://hashcat.net/forum/thread-4161.html


INFO: approaching final keyspace, workload adjusted


Session.Name...: oclHashcat
Status.........: Running
Input.Mode.....: Mask (7|8|9|3|10|6|2|1|11|12|4|5|0) [37] (0.00%)
Hash.Target....: 74e73c5d84a25af75ecf52c10426566a787e7ac2
Hash.Type......: SHA1
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...: 0 H/s
Speed.GPU.#2...: 0 H/s
Speed.GPU.#3...: 0 H/s
Speed.GPU.#*...: 0 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 1/1 (100.00%)
Skipped........: 0/1 (0.00%)
Rejected.......: 0/1 (0.00%)
HWMon.GPU.#1...: 0% Util, 36c Temp, 33% Fan
HWMon.GPU.#2...: 0% Util, 40c Temp, 20% Fan
HWMon.GPU.#3...: 48% Util, 32c Temp, 20% Fan

If you use -a 3 (mask-attack) it will work because the limit with mask attack is 55.

root@et:~/oclHashcat-1.36# ./oclHashcat64.bin -m 100 hash '8|7|9|4|2|10|6|11|12|1|0|5|13|3|14' -a 3 -w 3 --potfile-disable
oclHashcat v1.36 starting...

Device #1: Tahiti, 2981MB, 1000Mhz, 32MCU
Device #2: Tahiti, 2981MB, 1000Mhz, 32MCU
Device #3: Tahiti, 2981MB, 1000Mhz, 32MCU

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/4098/m00100_a3.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (227716 bytes)
Device #1: Kernel ./kernels/4098/markov_be_v1.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (35108 bytes)
Device #2: Kernel ./kernels/4098/m00100_a3.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (227716 bytes)
Device #2: Kernel ./kernels/4098/markov_be_v1.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (35108 bytes)
Device #3: Kernel ./kernels/4098/m00100_a3.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (227716 bytes)
Device #3: Kernel ./kernels/4098/markov_be_v1.Tahiti_1573.4_1573.4 (VM)_1428240294.kernel (35108 bytes)


ATTENTION!
The wordlist or mask you are using is too small.
Therefore, oclHashcat is unable to utilize the full parallelization power of your GPU(s).
The cracking speed will drop.
Workaround: https://hashcat.net/forum/thread-4161.html


INFO: approaching final keyspace, workload adjusted

903b8b9cbd54b01dce32d0038821a7725c97806a:8|7|9|4|2|10|6|11|12|1|0|5|13|3|14

Session.Name...: oclHashcat
Status.........: Cracked
Input.Mode.....: Mask (8|7|9|4|2|10|6|11|12|1|0|5|13|3|14) [34]
Hash.Target....: 903b8b9cbd54b01dce32d0038821a7725c97806a
Hash.Type......: SHA1
Time.Started...: 0 secs
Speed.GPU.#1...: 0 H/s
Speed.GPU.#2...: 0 H/s
Speed.GPU.#3...: 0 H/s
Speed.GPU.#*...: 0 H/s
Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.......: 1/1 (100.00%)
Skipped........: 0/1 (0.00%)
Rejected.......: 0/1 (0.00%)
HWMon.GPU.#1...: 89% Util, 49c Temp, 51% Fan
HWMon.GPU.#2...: 89% Util, 52c Temp, 57% Fan
HWMon.GPU.#3...: 90% Util, 51c Temp, 55% Fan

Started: Sun Apr 5 23:37:47 2015
Stopped: Sun Apr 5 23:37:49 2015