[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <loom.20130417T213533-340@post.gmane.org>
Date: Wed, 17 Apr 2013 20:18:39 +0000 (UTC)
From: john user <johnuser1243@...oo.com>
To: john-dev@...ts.openwall.com
Subject: Re: Bug report: specific hex salted hash failure
jfoug <jfoug@...> writes:
>
> This patch should correct this problem.
>
> Attachment (JtR_Bleeding_Dynamic_Salt2_UserID_Salt_Bug.patch):
application/octet-stream, 3212 bytes
--- get bleeding-jumbo and test the patch
git clone git://github.com/magnumripper/JohnTheRipper -b bleeding-jumbo
bleeding-jumbo
go to src dir and see patch was already in.
make linux-x86-64
bleeding-jumbo/run/john --wordlist=mywords --format=dynamic_1007 inhashes.txt
No password hashes loaded (see FAQ)
look at bleeding-jumbo/doc/FAQ
Q: Why doesn't John load my password file?
check my files
cat mywords
testme
cat inhashes.txt
5dd8145e0d1e2499bce05dcb4bce5cdf$HEX$24324f
-- next test does my build even work with dynamic_1007?
bleeding-jumbo/run/john --test
Benchmarking: dynamic_1007 md5(md5($p).$s) (vBulletin) [128/128 SSE2
intrinsics 10x4x3]... DONE
Many salts: 11289K c/s real, 11289K c/s virtual
Only one salt: 4032K c/s real, 4032K c/s virtual
yes
-- playing around found it can load only when the following string is in the
hash file
$dynamic_1007$5dd8145e0d1e2499bce05dcb4bce5cdf$HEX$24324f
could it also load hashes not prefixed by the $format$ string (especially
when format is specified on the command line) - seems to have this behavior
in jumbo-7 which previously I used.
If this load issue could have a fix then it would be appreciated
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.
