[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f16c434f941516b95099dd8a934eff5e@smtp.hushmail.com>
Date: Sun, 27 Jan 2013 15:11:37 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: krb5-23 or wow bug (or what?)
On 27 Jan, 2013, at 15:03 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
> On Sun, Jan 27, 2013 at 7:18 PM, magnum <john.magnum@...hmail.com> wrote:
>> On 26 Jan, 2013, at 13:54 , magnum <john.magnum@...hmail.com> wrote:
>>> I am actually trying to find some format thrashing memory. Under OSX the krb5-23 format fails, only on OMP builds (but even when OMP_NUM_THREADS=1) and only during --test (all formats). And this problem goes away if I register the krb5 formats before the plugins, so it is one of the plugin formats that thrashes memory.
>>
>> This drives me nuts. I have narrowed it down to wow-srp. If wow-srp self-test runs before krb5-23's, the latter fails cmp_all(1). If I disable wow-srp, the problem is gone.
>>
>> GMP or not doesn't matter.
>> OMP needs to be enabled, but it happens with OMP_NUM_THREADS=1 as well so it's not a thread safety issue.
>>
>> I can't reproduce it on Linux. And Valgrind does not help me (actually under Valgrind the bug does not even show). And making wow's buffers a lot larger does not make the problem go away.
>>
>> I'm stumped. Dhiru, can you try to reproduce this on OSX?
>
> I get access to OSX VM if my brother is not playing online games on that PC ;)
>
> To reproduce this problem, I need to make an OMP build and run "john
> -t=0", correct?
Yes, and you need libkrb5. To make it quicker, you can delete all plugins except wow, and comment out the dynamic formats registration in john.c.
magnum
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.
