hashcat v0.44, oclHashcat-plus v0.14 and oclHashcat-lite v0.15

[atom]

---

hashcat v0.44:

Download here: http://hashcat.net/hashcat/

type: feature
file: hashcat-cli
desc: added mode -m 9999 = Plaintext
trac: #45

type: feature
file: hashcat-cli
desc: added mode -m 5500 = NetNTLMv1 + ESS
trac: #96

type: feature
file: kernels
desc: added -m 5700 = Cisco-IOS SHA256
cred: philsmd

type: change
file: hashcat-cli
desc: changed the hash-format for NetNTLMv1 and NetNTLMv2 to .lc format
cred: #98

type: bug
file: hashcat-cli
desc: fixed bug in 32 bit version, did not crack -m 1800 sha512crypt
trac: #92

type: bug
file: hashcat-cli
desc: fixed bug in NetNTLMv2 parser
trac: #95

---

oclHashcat-plus v0.14:

Download here: http://hashcat.net/oclhashcat-plus/

type: driver
file: host programs
desc: added support for AMD ADL v5.0 library

type: feature
file: hashcat-cli
desc: added mode -m 5500 = NetNTLMv1-VANILLA / NetNTLMv1+ESS
trac: #51
trac: #96

type: feature
file: hashcat-cli
desc: added mode -m 5600 = NetNTLMv2
trac: #56

type: feature
file: kernels
desc: added -m 5700 = Cisco-IOS SHA256
cred: philsmd

type: feature
file: kernels
desc: modified -m 5100 = Half MD5 so that it accepts only 16 byte input, see next change why
trac: #89

type: feature
file: kernels
desc: modified -m 5100 = Half MD5 so it can crack middle and right portions, too (not just left)
trac: #89

type: bug
file: kernels
desc: fixed bug in NVidia version had to switch back to bitness-depending kernels

type: bug
file: kernels
desc: fixed bug in NVidia version writing to constant memory from kernel isnt allowed

---

oclHashcat-lite v0.15:

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

type: driver
file: host programs
desc: added support for AMD ADL v5.0 library

type: feature
file: hashcat-cli
desc: added mode -m 5500 = NetNTLMv1-VANILLA / NetNTLMv1+ESS
trac: #51
trac: #96

type: feature
file: hashcat-cli
desc: added mode -m 5600 = NetNTLMv2
trac: #56

type: feature
file: kernels
desc: added -m 5700 = Cisco-IOS SHA256
cred: philsmd

type: feature
file: kernels
desc: modified -m 5100 = Half MD5 so that it accepts only 16 byte input, see next change why
trac: #89

type: feature
file: kernels
desc: modified -m 5100 = Half MD5 so it can crack middle and right portions, too (not just left)
trac: #89

type: bug
file: kernels
desc: fixed bug in NVidia version had to switch back to bitness-depending kernels

type: bug
file: kernels
desc: fixed bug in NVidia version writing to constant memory from kernel isnt allowed

type: bug
file: hashcat-cli
desc: fixed bug in benchmark-mode, do not run MD5 again at end

type: bug
file: hashcat-cli
desc: fixed bug in benchmark-mode, Memory stepping when doing a benchmark
trac: #57

[Hash-IT]

Thank you once again atom.

You seriously disrupt my schedule with new releases.

Now I can't go out as I have to play with these.

[Hash-IT]

Is this for real ?

24 hours after atom releases new software for us all, FOR FREE and up to now I am the only one who says thank you ?

No one else using hashcat or oclhashcat anymore ?

[K9]

Thanks. :p

[spog]

thank you, great work

[KT819GM]

Would like to thank also and hope will have possibility to use suite again soon on my damn new (and horrible bad working) workstation.

[Mem5]

Awesome, thank you

[philsmd]

@Hash-IT, I do *not* think that there are only few people that use hashcat or oclHashcat anymore, instead I think there is a FAST increasing number of users *every* day...
Maybe atom has a number (i.e. an estimate) e.g. of the exact number of downloads etc for instance after the last release... I really think the user base is almost uncountable. YES it is, believe me!

What regards myself, I didn't post here so far (but I retweeted etc the news) because I thought I don't want to "just" say "Thank you" (what could be seen, at least in other forums, as spam and not very useful for others)... maybe here (in this forum) it is different and I *LIKE* that attitude if so.

But now my appreciation:
1. I stressed atom *a lot* the few days because of Cisco type4 etc (then there was also my x32 Nvidia problem that he fixed VERY quickly, I think it was this thread: http://hashcat.net/forum/thread-2040-page-3.html )
2. we had a lot to do to communicate to Cisco - Responsible Disclosure - etc.... and he WORKED/HELPed a lot!!! ... and to answer the dozens of mails of news magazine/blogs etc, again for Cisco sha256 type 4
3. he meanwhile implemented NetNTLM v1 / v2 (how could you make this @atom? during this busy time?)
4. he optimized NetNTLM wherever possible. AMAZING!!!
5. he (also) did several bug fixes etc (see trac)...

So the only thing left to say: THANK you, THANK you, THANK you atom.
Really great job!!! and very professional how you did handle all this problems (where I could be seen as a problem maker somehow,hehe)

Best

[Hash-IT]

@philsmd

My post was somewhat of a rhetorical question.

Also posting to say thank you is never considered spam, it's just good manners.

.... As you can probably tell, I'm English and we get quite hung up on this sort of thing

[philsmd]

@Hash-IT yes, you are right. At least you did understand what I was trying to say, but yes SPAM is something *else*...

Again, I think atom knows how valuable his work is for MANY of us!