UPDATE: cRARk author just contacted me about the problem on NVIDIA hardware:
As for fail on NVIDIA cards, it’s so simple in it’s written in the FAQ – you need to run driver-timeout.reg and reboot. (RAR kernel is so long and Windows can’t wait so much 😉
Indeed it’s simple when you know it 😀
cRARk is a free password cracker (or recovery tool ;)) for RAR archives. One interesting feature is the support of OpenCL for accelerating the cracking (for AMD Radeon and NVIDIA GeForce cards). CUDA is also supported for NVIDIA cards.
cRARk is a command line tool and is very easy to use. If the password is not too long (less than 6 characters) you have many chances to find it with cRARk.
I tested the tool with a simple RAR file with the following password: toto. I first tested on a GeForce GTX 580 but without success. No matter the GPU computing API used (OpenCL or CUDA), there was still an error:
On a Radeon HD 6970 (with Catalyst 11.10 Preview 3), on the other hand, the OpenCL version of cRARk worked perfectly fine! Then I cracked my simple test file in 39 seconds. To find the password toto, cRARk has tested 411489 passwords at the rate of 10438 passwords / second.
OpenCL version + HD 6970
The second test I did with the Radeon HD 6970 is to crack another RAR file, this time with the following password: t4t4:
OpenCL version + HD 6970
The time to find the password was a bit longer (1min 37sec) but the tool did it!
This test confirms that AMD Radeon cards are still the hardware of choice for crackers (see this article: Radeon HD 5970: the Ultimate Password Cracking Hardware?)!
Where can you find cRARk? Really simple, just visit this page: cRARk: Fastest utility to crack RAR password.
17 thoughts on “(Tested) cRARk, OpenCL Password Cracker for RAR files (***Updated***)”
You should introduce +1 button for ur site and for all articles 🙂
You should introduce +1 button for ur site 🙂
Added at the end of every post!
What about longer passwords?
Also what about a comparison of a fast cpu vs the 6970? 🙂
With my 450 it works with CUDA but takes to much time for 6 characters and even if my password is of 4 chars like ‘q2w1’, its starts testing for password length 5!!. Isn’t this some kinda bug?
I tested on my gtx460 , password “toto” find on 1:32 ,rate=4161p/s
Psolord: heres an article discussing wifi cracking on gpus, theres some tables that show how much longer 2 extra characters will take..
as ya can see just adding 2 more characters to the password, increases the time needed exponentially
uh, no sorry, if yu need to adjust the tdr timeout config then the application is just fucked.
Do not know why it’s asking for “password.def” and this file isn’t present in the directory.
Victor: you have to rename the english.def file in password.def.
What this is for? i mean what to i gain craking pass from video cards? (sorry for my ignorance)
@JeGX, thanks ))
@Gr – it’s useless until you got some pass protected RAR file with =<6 pass length and you want to look inside them. I have no need for that since I use 7z with some 18 char pass so not even supercomputer could compute correct pass in time 😉
@Promilus, yes )), and if you’re using chars like ~$@&~ in the password, you’re in trouble ))
Passwords tested = 999542 (time = 01:53.73, rate = 8789 p/s)
this is very helpful. my passwords checked.thanks
I tested mey password, for other website.. i like it
Comments are closed.