oclHashcat-lite v0.09

[atom]

Hello Hashcat-Users,

I am proud to announce version 0.09 of the oclHashcat-lite series.

Download it here: http://hashcat.net/oclhashcat-lite/

The highlights of this release are:

• Support for AMD GCN cards (hd7xxx series)
  

I already wrote some more detailed informations about the integration here: http://hashcat.net/forum/thread-817.html

This card is a true DES killer. I wrote some more detailed informations about this topic here: http://hashcat.net/forum/thread-846.html

• Added the LM Algorithm
  

After so many people requested this algorithm in the feature request section I decided to add it even I had not interesst in it.

However, it turned out it was a good investment of time. I realized how many pentester still have need for it.

See here for discussion: http://hashcat.net/forum/thread-167.html

• Vectorized datatype kernels for sm_21 NVidia architecture
  

This a massive improvement for low- and mid-ranged NVidia GPUs.

The gtx560Ti @ MD5, for example, increased by 23% (1252 Mhash/s -> 1660 Mhash/s).

This improvement can be seen on nearly all algorithms for this architecture.

• MD4 based algorithm tuning
  

To make it short: I found a way to reverse another step in MD4.

Especially the NTLM and DCC algorithm benefit from this code change.

The hd6990 @ NTLM broke the 20000 Mhash/s mark on stock clocks. Average increase is around + 9% (19100 Mhash/s -> 20864 Mhash/s).

• Updated EULA
  

This goes back to a discussion we had HD Moore from Rapid7.

The updated EULA is a lot more relaxed for professional pentesters than before.

See changelog for more details.

• Fixed some major issues
  

On thing that many user complained about in oclHashcat-lite 0.08 was its "instability" and problems with session restore.

This popped in because of a default-settings change in oclHashcat-lite v0.07. It has been set back to oclHashcat-lite v0.06 default.

Discussion can be found here: http://hashcat.net/forum/thread-681.html

• Harmonization with oclHashcat-plus
  

The --help page, the --outfile-format and the -m parameter values, in case of an overlap, are now equal to oclHashcat-plus v0.08.

It will help to avoid confusion, thats why I am planning to do the same change on CPU hashcat in the next version.


Full changelog:

Code:

type: feature
file: kernels
cred: added -m 2811 = IPB 2.0, MyBB1.2

type: feature
file: kernels
cred: added -m 3000 = LM

type: driver
file: kernels
desc: added support for AMD APP SDK 2.6

type: driver
file: kernels
desc: added support for NVidia CUDA 4.1

type: feature
file: kernels
desc: added support for AMD GPU's "Devastator" and "Scrapper"

type: feature
file: kernels
desc: added support for AMD GPU's "Capeverde", "Pitcairn" and "Tahiti"

type: feature
file: host programs
desc: backported --outfile-format from oclHashcat-plus v0.07

type: feature
file: host programs
desc: backported --seperator-char feature from hashcat v0.38
cred: thorsheim

type: feature
file: host programs
desc: add support for passwords smaller length 4

type: bug
file: host programs
desc: fixed issue with unaligned --pw-skip, did not auto-shutdown when 100% keyspace reached
cred: MrUltimate

type: bug
file: host programs
desc: fixed issue when using --pw-skip-plain in combination with --hex-charset

type: change
file: host programs
desc: changed hash parser for Joomla hashes to allow salt-length of 16 - 32
cred: sono

type: change
file: host programs
desc: changed default setting for CPU affinity: Linux unlocked, Windows unlocked

type: change
file: host programs
desc: ETA is now calculated regarding to configured value of --pw-skip and --pw-limit
cred: MrUltimate

type: change
file: host programs
desc: changed restore-timer default value to 60 due to GPU utilization issue
cred: MrUltimate, d-unknown, khempanhom

type: change
file: host programs
desc: EULA. Removed sections 2, 6, 8 and 9. Relaxed sections 3 and 7.
cred: hdmoore

type: change
file: kernels
desc: renamed -m 1    to -m 10
desc: renamed -m 3    to -m 2600
desc: renamed -m 5    to -m 2611
desc: renamed -m 15   to -m 2711
desc: renamed -m 101  to -m 110
desc: renamed -m 600  to -m 101
desc: renamed -m 700  to -m 111
desc: renamed -m 1300 to -m 131
desc: renamed -m 2000 to -m 112
desc: renamed -m 2300 to -m 132

type: change
file: rules
desc: redesigned usage screen
cred: http://hashcat.net/forum/thread-716.html

--
atom

[chort]

A quick note on LM: When you do a mask attack the same mask applies to both halves of the hash, so using masks longer than 7 characters is pointless (and will not do what you expect).

[mastercracker]

Hmm. For the LM mode, It probably would have been better to make the user split their hashes in 2 and use that input format instead. However, if you really want to keep this format (which has the advantage of being easier for the user since he does not have to keep track of 2 hashes), it needs to be able to output only half of a cracked password in the event that only 1 part is recovered. Besides that, it's great, I can cover the whole regular keyspace in a bit more than 3 hours.

EDIT: Finally, it does not output the results of both halves so there is a bug.

[Mem5]

Thanks atom !

I am not agree with you mastercracker, if you have a long list of 32-chars hashes you obviously do not want to split all hashes in 2. Also, for found hashes it better to have the entire LM hash:plain : otherwise how can we know which part of the hash has been cracked when you have thousands of hashes ?..

[mastercracker]

otherwise how can we know which part of the hash has been cracked when you have thousands of hashes ?..

There are multiple ways that it can be represented. One example could be like this:

1234567890abcdef1234567890abcdef:<NOT CRAKCKED> DMIN1

or

1234567890abcdef1234567890abcdef:1SUPERA <NOT CRACKED>

Also, maybe not for you but when you try to help other people, they sometime make a typo in their hash. By having at least a part of the password allows you to know that the hash has been properly extracted (and not syskeyed) and guess what the other part could be. Don't get me wrong, I am not against a hash in one piece, I just state some drawbacks.

[atom]

mastercracker: plus will do that

[mastercracker]

mastercracker: plus will do that

Thanks, that answers also my question in the featured request section.

[Mem5]

Ok, that's nice too. Actually with lite version when the right part of LM hash is not cracked but the left one is, the result is not displayed.

[bobili]

thx for this great program atom.. this is my speed for SL3 bruteforce...

and this is graphic card's that I use.
temperature are 65C maximum..



how to put multiple files to run one after another?

[KT819GM]

You understand how to use linux, how to install driver, how to connect 5 cards to work on one machine, but don't know anything about bash?? Maybe if you try to put not one but two lines on your .sh file maybe it should do the trick?