Date: Sat, 20 Apr 2013 17:31:39 -0400 From: <jfoug@....net> To: john-dev@...ts.openwall.com Subject: Re: Re: Bug report: specific hex salted hash failure additional issue ---- john user <johnuser1243@...oo.com> wrote: > jfoug <jfoug@...> writes: > > > > This patch should correct this problem. > > Thank you for the updates. > Much better results with this patch included. > can I report another salted hash issue found however. > > $dynamic_1007$413fc6e2e1e92ca167b58391768901dc$HEX$3a322c:,:@ > > md5(md5($p).$s) > > $p ,:@ > $s :2, > > john --wordlist=mywords --format=dynamic_1007 inhashes.txt > Loaded 1 password hash (dynamic_1007 md5(md5($p).$s) (vBulletin) [128/128 > SSE2 intrinsics 10x4x3]) > guesses: 0 time: 0:00:00:00 DONE (Sat Apr 20 10:24:57 2013) c/s: 50.00 > trying: ,:@ > > cat mywords > ,:@ > > cat inhashes.txt > 413fc6e2e1e92ca167b58391768901dc$HEX$3a322c $ ../run/john -w=mywords -form=dynamic_1007 inhashes.txt Loaded 1 password hash (dynamic_1007 md5(md5($p).$s) (vBulletin) [128/128 SSE2 intrinsics 480x4x3]) ,:@ (?) guesses: 1 time: 0:00:00:00 DONE (Sat Apr 20 16:25:22 2013) c/s: 1.39 trying: ,:@ Use the "--show" option to display all of the cracked passwords reliably Worked fine for me. my build is current john bleeding tree. Also, make sure your dictionary actually contains that line with only 3 characters, and does not have some trailing space on the line, or something like that. Jim.
Powered by blists - more mailing lists
Powered by Openwall GNU/*/Linux - Powered by OpenVZ