RAR hash cracking problems
#2
-m 12500 supports a max of 20 chars in -a 0, so your candidates shouldn't be rejected. And indeed I cannot reproduce this with 1.37 using the command you provided:

Code:
sagitta@inceptus:~/cudaHashcat-1.37$ maskprocessor/src/mp64.bin -i 18:26 -1 ?l?s password?1?1?1?1?1?1?1?1 | ./cudaHashcat64.bin --quiet --status -m 12500 rar.test
^C
Session.Name...: cudaHashcat
Status.........: Aborted
Input.Mode.....: Pipe
Hash.Target....: ...
Hash.Type......: RAR3-hp
Time.Started...: Sat Oct 17 00:34:23 2015 (12 secs)
Speed.GPU.#1...:     9429 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 79872
Rejected.......: 0
HWMon.GPU.#1...: 91% Util, 59c Temp, 26% Fan

But let's talk about that command, because it doesn't make any sense.

First, you're telling maskprocessor to increment from length 18-26, but your mask is only 16 chars long. And that's on top of the fact that there's absolutely no reason to use maskprocessor here at all. You also don't need to specify -p or --outfile-format, and your --gpu-temp-abort value is insanely low. And what happened to device 7?

Fixing your command for you:

Code:
cudaHashcat64 -a 3 -m 12500 -o C:\cracked\rarhash.txt -w 3 -1 ?l?s C:\hashes\11122.txt password?1?1?1?1?1?1?1?1

And this leads us to your final and biggest problem: that keyspace is way too big. You're trying to brute force 59^8 on a very slow algorithm. Even if you had 8x Titan X this would take 35 years (or, you would need 280x Titan X to exhaust this keyspace in one year.)


Messages In This Thread
RAR hash cracking problems - by crypted.wolf - 10-17-2015, 08:53 AM
RE: RAR hash cracking problems - by epixoip - 10-17-2015, 09:52 AM
RE: RAR hash cracking problems - by crypted.wolf - 10-17-2015, 10:21 AM
RE: RAR hash cracking problems - by epixoip - 10-17-2015, 10:38 AM
RE: RAR hash cracking problems - by crypted.wolf - 10-17-2015, 12:30 PM
RE: RAR hash cracking problems - by epixoip - 10-17-2015, 01:15 PM