A million little bugs - hashcat dev

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.3. This step is absolutly neccessary otherwise you will not find the code and you will not get a error message!
Get oclHashcat-lite v0.2 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 (IMEI). Its a 14 char hex-encoded string and looks like this: 35152304783734
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 101 -n 160 -1 00010203040506070809 --pw-min=15 --pw-max=15 --hex-charset --hex-salt --output-format=1 --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 101: This sets the hash-type of oclHashcat-lite. SL3 uses the sha1($pass.$salt) scheme.
-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)
--pw-min=15 --pw-max=15: We want to crack a Password with length 15. SL3 Passwords have a static length: 15. If you do not specify it starts with length 4 and ends with length 15. Its good in password cracking but useless in SL3.
--hex-charset: Tells oclHashcat-lite that our charset is given in hex
--hex-salt: Tells oclHashcat-lite that our salt is given in hex
--output-format=1: This is important! Otherwise the output is ascii encoded and useless for SL3
--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

http://hashcat.net/forum/thread-366.html

The whole testing and bugfixing is finished, atom released oclhashcat-lite!

You can download it at http://hashcat.net/oclhashcat-lite/

Cheers atom!

The new SDK is out now! http://developer.amd.com/gpu/AMDAPPSDK/Pages/default.aspx

It may be only hours till the new hashcat release, be prepared!

atom> AMD APP intends to deprecate the following as of SDK 2.5:
atom> ??? AMD CAL
atom> LOOOL
atom> they want to kick out CAL

UPDATE:
Atom released quick review on the new SDK.

AMD APP SDK v2.4 released
Finally, they released it. The long awaited SDK that should patch all Bugs. Guess what: not a single Bug fixed!

Here are the unresolved issues that are related to oclHashcat:

Most Important:

Quote:
The ATI Radeon™ HD 5970 GPU is currently supported in single-GPU mode only. It is recommended users only access the first device on an ATI Radeon™ HD 5970 GPU for GPU compute.

Well this is a Problem for oclHashcat, but we have that hack, that hidden environment variable "GPU_USE_SYNC_OBJECTS". Using it we are able to utilize the 2nd GPU fully. It has been tested several times. It works fine. However its inofficial.

Semi Important:
bitselect() still not mapped to BFI_INT. Thats sad, would save me a lot of work. So that means i still have to hack the BFI_INT instructions into the binaries.
clGetDeviceInfo CL_DEVICE_MAX_CLOCK_FREQUENCY returns 0mhz, sometimes i've seen 1mhz. Its not listed in the in the release notes, but its still there.
Quote:
The OpenCL runtime currently exposes less than the total amount of memory physically available on the card

Last but not least, SDK v2.4 had something usefull:
Added support for BeaverCreek, Caicos, Turks and WinterPark GPUs.

Some additionally notes from me. In the developer release notes they say:

Quote:
AMD APP intends to deprecate the following as of SDK 2.5:
– AMD CAL
– Support for the Windows XP platform
– BIF 1.0 (the binary format prior to SDK 2.2)

All of the following points are interessting from our view:
Kick out CAL? I guess some guys in the GPGPU scene really do not like to read this! Just to name some of them: IGHASHGPU, KK, Fenix or calpp version of Pyrit base on it.
Kick out Windows XP support. Thats not so bad however i know some Hashcat users still use XP. Guys, upgrade to Win7 or Linux
Kick out BIF 1.0. Well thats a problem for oclHashcat. They all use the binary format. But I hope they stick at least to ELF. At least that means new releases of all oclHashcats after AMD releases SDK 2.5

Also it seems they finally renamed that ATI to AMD in the SDK. That means, on Linux, you have to replace the files from the ICD registration on /etc/OpenCL/vendors. Remove the old ones and unpack the icd-registration.tgz in the SDK 2.4.

Thats all from my first impressions. However it will not prevent me from releasing oclHashcat-lite. I guess on weekend

--
atom

http://hashcat.net/forum/thread-355.html

Atom implemented so called session in oclhashcat-lite.
A session is nothing more then the default implementation of the restore feature with the possibility to manage multiple sessions.
It's a pretty handy feature that i think will be frequently used.
Here is an example of how it will work:

oclhachcat-lite64.bin --session site01.oclhc --restore

In the meantime a beta tester confirmed that hashcat pefroms well on the ATI 6990, no problems at all!

Another maybe even more interesting new part especially of the lite version is a protection against crackers. After a session with atom i came up with a way to protect hashcat against such hillarious things that happened two weeks ago. I don't want to go in the detail but, atom has adpted my advice, enhanced it, implemented it and gave it two "real" crackers to check if it would work. One of the crackers couldn't do the job and the other one sayed that he just had a little luck. The one that got it gave the last hint to make it really hard for others to copy this piece of software.
So long, if these guys out there are such good to get it, they should do some more constructive things instead!

Big thanks to the two guys that gave us their time!