hashcat v0.41
#1
* changes v0.40-> v0.41:

First Hashcat release to support AVX and XOP!

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

Code:
type: feature
file: host programs
desc: added support for AVX and XOP instruction set

type: feature
file: hashcat-cli
desc: added wide-character support to table-lookup attack engine
cred: epixoip

type: feature
file: host programs
desc: optimized word-generator in -a 3 mode

type: feature
file: host programs
desc: change potfile format to hash:password
cred: m4tr1x

type: feature
file: hashcat-cli
desc: added mode -m 122: OS X v10.4, 10.5, 10.6
cred: radix

type: feature
file: hashcat-cli
desc: added mode -m 1722: OS X v10.7
cred: radix

type: feature
file: hashcat-cli
desc: added mode -m 50: HMAC-MD5 (key = $pass)

type: feature
file: hashcat-cli
desc: added mode -m 60: HMAC-MD5 (key = $salt)

type: feature
file: hashcat-cli
desc: added mode -m 150: HMAC-SHA1 (key = $pass)

type: feature
file: hashcat-cli
desc: added mode -m 160: HMAC-SHA1 (key = $salt)

type: feature
file: hashcat-cli
desc: added mode -m 1450: HMAC-SHA256 (key = $pass)

type: feature
file: hashcat-cli
desc: added mode -m 1460: HMAC-SHA256 (key = $salt)

type: feature
file: hashcat-cli
desc: added mode -m 1750: HMAC-SHA512 (key = $pass)

type: feature
file: hashcat-cli
desc: added mode -m 1760: HMAC-SHA512 (key = $salt)

type: feature
file: hashcat-cli
desc: added mode -m 1731: MSSQL 2012
cred: radix

type: bug
file: hashcat-cli
desc: Fixed a bug when using -e with salted sha256 or sha512
cred: Rub3nCT

--
atom
#2
Good job! Thanks!
#3
very nice Smile
#4
Bulldozer users, try this cat out, the speed on some algos(*cough* *cough* sha512) is jawdropping.
#5
Quote:desc: change potfile format to hash:password
This point is a downgrade for me. It makes it impossible to use the pot file as dictionary. Sad
#6
use
Code:
cut -d: -f2-99
#7
Thanks a lot for this update, appreciated :-)

Beside, sorry to missunderstand the fact of K9 comments, can you please explain :

In the -help of this version compared to the 4.0 version for me is the same :

--output-format=NUM 0 = hash:pass

so, what mean "hash:password" & "hash:pass" ? the same they are not ?

***********
Concern, this part of this option, for me an + can be to have ( in addition with the hashe:pass format for sure) the output in "pass" only without hashes, even this one is allready present in the pot file &/or can be tweaked with the "Mem5" command on the output file.

& for using the pot file as dictionnary, i haven't any prob to use it : i just type "hashcat.pot" as dic...Mhmmm maybe i miss something, or my English understanding default...!
#8
Im using the potfile as wordlist. I know you can change the outfile but its a different file.

Quote:cut -d: -f2-99
It shouldn't be a problem to edit it. Its jsut another useless step which takes time and maybe kills some passwords. How about some command to keep the potfile in pass only. It would be easier and faster while cracking hashes for me.