oclHashcat-lite SL3 cracking howto

[atom]

I know we have a lot of new users from gsmhosting because of SL3 cracking. Welcome guys!

Before we get bombed with questions i decided to write a small howto.

Yes, the latest oclHashcat-lite is able to crack SL3! But please keep in mind oclHashcat-lite was not specially designed to crack SL3.

If you want an easy-to-use-one-click solution: buy one. There a diffrent commercial solutions out.

Ok, lets start:

• AMD/ATI Users only: Get latest catalyst driver! Minimum 11.4. This step is absolutly neccessary otherwise you will not find the code and you will not get a error message!
• Get oclHashcat-lite v0.6 from Homepage and unpack it
• Open command shell window and cd to oclHashcat-lite installation directory
• Get your hash (SHA1). Its a 40 char hex-encoded string and looks like this: 21B1E417AF2DE6496772BCC2FE33D2593A9BB7A0
• Get your salt (its your IMEI). Its a 15 char hex-encoded string and looks like this: 351523047837342 but you only use the first 14 chars from it. the last one is just a checksum value and we dont use it.
• Prepare your salt. Prepend and Append 00 to the salt like this: 003515230478373400
• The following command starts oclHashcat-lite. Its a complicated looking string but its static, it does not change. The only thing that changes is your hash and your salt. The smart user put it into a .bat file!
  

Quote:oclHashcat64.exe -m 1900 -n 160 -1 00010203040506070809 --output-file=out.txt 21B1E417AF2DE6496772BCC2FE33D2593A9BB7A0:003515230478373400 ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1

The linux command is exactly the same. I will explain the parameters so you know what you are doing:

• -m 1900: This sets the hash-type of oclHashcat-lite. 1900 stands for SL3.
• -n 160: This is the workload-amplifier and its the most important flag that controls the Performance of the program. If you want more speed, raise it. If you want less speed, lower it. This is if your desktop is lagging to much.
• -1 00010203040506070809: This binds the charset to our custom charset 1. SL3 uses only a small charset of ten chars (0-9, binary encoded)
• --output-file=out.txt: This is where the cracked pass is stored to
• 21B1E417AF2DE6496772BCC2FE33D2593A9BB7A0:003515230478373400: The only thing that changes.
• ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1: its our "mask". 15 times ?1 (which ist custom charset 1 we bound before)
  

Of course there are a lot of options to optimize the attack, use it in distributed mode, restore sessions... Stuff like that.

Please play around a bit with it before asking Questions. Its really not that hard.

--
atom

[RAM]

for much optimized config try this..

xxxHashcat-lite32 0FB003wsdeddfe04de320C9E0:003512345678913200 -1 00010203040506070809 --pw-min=15 --pw-max=15 -m 101 ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1 -n 800 --hex-salt --hex-charset --output-format=1 --output-file=out.txt

use "-n 800" with out the quotation for much faster and optimized calc speed... but be sure you have the proper cooling for your cards...

i hope am correct for i just read it on the other side of the world

thanks
RAM

[atom]

(04-11-2011 12:30 PM)X-Shadow Wrote: ʉۢ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1: its our "mask". 15 times ?1 (which ist custom charset 1 we bound before)

You put an extra "?1" (they are 16 times ?1)

thanks man! fixed.

(04-11-2011 12:30 PM)X-Shadow Wrote:  Anyway, where is your Donate Button?

Lovin' it!

B.R.

there is none, i am not interessted in making money with this project. but thanks!

[d-unknown]

thanx atom for the software
just tested it with my 2 hd5970 oc'ed to 750mhz, i get like 5900m hashes/sec which is almost 1200m hashes/s better than other tools
hope you develop one day and when you'll have time a GUI version for lazy peoples

just a remark about the -n value (workload amplifier), i get same amount of hashes/s with -n as 160,100 or 30
with 160 my computer is unusable , too much laggy, but with 30 it's ok, but it doesn't affect global hash speed whatever is the value
last think you might consider, the most important when bruteforcing with ATI cards , it's gpu temperature, and even more important, VRM temps too, gpuz is a good tool to monitor them
according to my own experience when VRM's get very hot like +100°, there a big chances to miss the sl3 code
so it will be very usefull if you add a monitoring feature in future updates

good luck

[atom]

thanks for the suggestion, i will have a look at it

[kaktus]

Thanks for this masterpiece of soft :-)

anyway I have 2 questions:

1. Is there any flag (I haven't seen it) to disable restore function? I don't won't that it's all the time refreshing that file in my folder.

2. Need thread for oclhashcat-lite speed comparison :-)
(5970 ~ 34 s)

cheers

[Moulnisky]

Hi,
Just to say thanks to Atom for this release.
The importance of his job is not only in performance increase and stability of the software (Actually I can say it is really great in both) But it is as well in giving us the trust and the cheance to use a good software without being insulted, accused of stealing and bad treated any time passing through the coder's forum or blog.
Been reading you don't want any donation or profit for this software and I do respect your choice but consider any time available, if ever needed, the computers I use at mine for calculations or testing.
Thanks again and BR
Alex

[atom]

(04-11-2011 05:58 PM)kaktus Wrote:  1. Is there any flag (I haven't seen it) to disable restore function? I don't won't that it's all the time refreshing that file in my folder.

never thought anyone does not want restore ability, so there is no specific option to disable it. if more people show interrest i will add it.

(04-11-2011 05:58 PM)kaktus Wrote:  2. Need thread for oclhashcat-lite speed comparison :-)
(5970 ~ 34 s)

start it

[atom]

the content of this thread has been moved to a dedicated wiki page:

http://hashcat.net/wiki/cracking_sl3

thread closed.