[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0FE694B9039A4422811A6C6CE05C7191@D9VGLK61>
Date: Thu, 24 Mar 2011 07:25:31 -0500
From: "JimF" <jfoug@....net>
To: <john-users@...ts.openwall.com>
Subject: Re: New John 1.7.6 OpenMP Binaries for MacOSX and Windows
From: "Solar Designer"
> On Wed, Mar 23, 2011 at 07:38:41AM -0500, jfoug wrote:
>> >From: websiteaccess
> [...]
>> >Loaded 1821691 password hashes with 196 different salts (Raw MD5 [gen])
> [...]
>> Using raw-md5 mode, by linking to md5_gen(0) functions
>> <b>with 196 different salts</b> (Raw MD5 [gen])
>>
>> Buggy behavior of md5_gen() only recently fixed. If there was any data
>> after the hash (GECOS stuff), then md5_gen was causing john to run the
>> multi-salt code.
>
> This means that john-1.7.6-jumbo-12-early-release-md5-gen-3 on the wiki
> is not suitable for actual use (it's just a development milestone).
I believe this problem is in the rawMD5_fmt.c code. The first patch of
that ran it's own salt function. Those function pointers have to link into
the md5_gen salt functions to work properly. I posted a patch for that as
an email, (twice). Here is from my March 3rd post about the same topic:
>The 'extra fix' I listed for the raw-md5 'thin' which was done in the SSE
>intrisic was not
>part of my -v3 patch, so yes, it would have to be done on its own. I do
>not
>think this was put into the sse-intrinsic patch after I listed it.
>
>That patch (from a prior email) is this, and it IS needed:
>
> static void rawmd5_init(void)
> {
> md5_gen_RESET_LINK(&fmt_rawMD5go, Convert(Conv_Buf,
> rawmd5_tests[0].ciphertext), "raw-md5");
> fmt_rawMD5go.methods.binary = rawmd5_binary;
>- fmt_rawMD5go.methods.salt = fmt_default_salt;
>+ fmt_rawMD5go.methods.salt = fmt_MD5gen.methods.salt;
> }
Jim.
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.
