Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sat, 19 May 2012 08:20:06 -0700 (PDT)
From: NeonFlash <psykosonik_frequenz@...oo.com>
To: "john-users@...ts.openwall.com" <john-users@...ts.openwall.com>
Subject: SHA1-Gen / Dynamic_25 Hashes

I am not clear what is going wrong here. Trying to crack hashes that have the SMF Forum format:

sha1(strtolower($user),$pass) and this matches, sha1($salt,$pass)

The username is the salt in this case. Ofcourse, I have converted the usernames to lowercase. I have tried both SHA1-gen and Dynamic_25 subformat, but it does not work for me. I do not get any error message, the hashing process shows no cracked hashes.

Please note: I know the passwords already and they are present in the wordlist I am using.

Using JTR verison: 1.7.9-jumbo-5

Here are the command line syntaxes. "xxx" is the username or salt in this case.


Case 1:


john --format=sha1-gen --field-separator-char=" " -w:wordlist.txt hashes.txt

The hashes are stored in the following format:

xxx $SHA1s$xxx$abac710fda8befcb4b8f3e96fb27a54f271b70a4

Case 2:

john --format=sha1-gen w-:wordlist.txt hashes.txt

Hashes are stored in the format:

$SHA1s$xxx$abac710fda8befcb4b8f3e96fb27a54f271b70a4

Case 3:


john --subformat=dynamic_25 --field-separator-char=" " -w:wordlist.txt hashes.txt

Hashes are stored in the format:

Case 4:

xxx $dynamic_25$xxx$abac710fda8befcb4b8f3e96fb27a54f271b70a4

john --format=dynamic_25 -w:wordlist.txt hashes.txt


Hashes are stored in the format:

$dynamic_25$xxx$abac710fda8befcb4b8f3e96fb27a54f271b70a4

As an example to show the output, for Case 1, I see:

using field sep char ' ' (0x20)
Loaded 6384 password hashes with 6384 different salts (Generic salted SHA-1 [32/
32])

This is weird.

My Processor is: AMD Athlon II X2 260 Processor 3.2 Ghz

OS: Windows 7 Ultimate, 64 bit

Thanks.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.