RAR crack
#1
Hello,

I'm trying to crack a .rar with hashcat. I extracted the hash with rar2john and deleted the extra characters (possible error location since I guessed).

rar2john provided lines like this:
filename.rar:$RAR3$*0*HASHLIKETEXT1*HASHLIKETEXT2:0::::filename.rar

and I changed to this:

$RAR3$*0*HASHLIKETEXT1*HASHLIKETEXT2

If I start hashcat with -a 3 -m 13000 it complains about the line length.
If I start hashcat with -a 3 -m 12500 it writes about kernel and device initialization, then the OS crashes.

I'm on Win7, tried 3.5.0 and 3.6.0. The NVIdia driver is up-to-date.

If I try to crack an MD5 or WPA it runs smoothly, only RAR cracking has problems.

Could you please help me to decide if the edited hash format causes the crashing or something else?

Thanks,
PMTU

Ps: according to the HashCat wiki, the format of hash is fine.
#2
There could be many reasons why your experiencing these crashes.

I would suggest that you try the -m 12500 = RAR3-hp example hash from https://hashcat.net/wiki/example_hashes.

It would be also interesting/helpful to know if you see any warnings from hashcat, e.g. for instance related to the timeout patch etc (did you apply this patch https://hashcat.net/wiki/doku.php?id=timeout_patch ?)
#3
(07-18-2017, 05:35 PM)philsmd Wrote: There could be many reasons why your experiencing these crashes.

I would suggest that you try the -m 12500 = RAR3-hp example hash from https://hashcat.net/wiki/example_hashes.

It would be also interesting/helpful to know if you see any warnings from hashcat, e.g. for instance related to the timeout patch etc (did you apply this patch https://hashcat.net/wiki/doku.php?id=timeout_patch ?)

Thanks, I will take a try with the example.
Yes, I applied that timeout patch.

On start the hashcat doesn't show any error or warning.

Update:
no, hashcat doesn't run with the example hash. Crashes the OS immediately.

Update2:
I tried a simple benchmark and there is at least one more algorithm that causes crash: PBKDF2-HMAC-SHA512

Once the benchmark process has reached this hash, the same happened.

Any idea how to debug? Can I provide any information that could help you to help me?