[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 15 Jul 2012 21:28:52 -0700 (PDT)
From: NeonFlash <psykosonik_frequenz@...oo.com>
To: "john-users@...ts.openwall.com" <john-users@...ts.openwall.com>
Subject: Re: Vbulletin Hashes not loading
Ok, this made it work.
I have included a username as well this time which formats the hash as follows:
user $dynamic_7$501652a767ad6a888b659fb1957cb063$)!!
then, I crack using:
john -w:wordlist.txt --format=dynamic_7 --field-separator-char=" " hash.txt
Isn't there an easier way to do it?
Based on my understanding, I guess this is happening because I am using dynamic_7 mode instead of dynamic_6. dynamic_7 forces the field separator character to be not a colon.
I wish dynamic formats were just as easy to handle as other hash types like DES, MD5, SHA1 and so on which are implemented in the core version of JTR.
________________________________
From: NeonFlash <psykosonik_frequenz@...oo.com>
To: "john-users@...ts.openwall.com" <john-users@...ts.openwall.com>
Sent: Monday, July 16, 2012 9:44 AM
Subject: [john-users] Vbulletin Hashes not loading
I am trying to crack Vbulletin hashes for version < 3.8.5 with a 3 byte salt.
I have formatted the hash as follows:
$dynamic_7$501652a767ad6a888b659fb1957cb063$)!!
now, I crack using:
john -w:wordlist.txt --subformat=dynamic_7 hash.txt
hash.txt contains the above hash.
It gives the error, no hashes loaded.
What might be wrong?
Do I need to specify the user id as well in the file and then specify a field-separator-char at the command line?
I thought we could load hashes into john without specifying the username as well.
Powered by blists - more mailing lists
Powered by Openwall GNU/*/Linux -
Powered by OpenVZ