[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP2655B9B42D8A132FFED2461FDE30@phx.gbl>
Date: Sat, 23 Jun 2012 15:18:25 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: segfault with ./john --test --format=md5ns caused
by commit aab646b42afe93ca909ba1a99bc0e2a1b027a79d
On 06/23/2012 12:16 PM, Frank Dittrich wrote:
> On 06/23/2012 12:02 PM, Frank Dittrich wrote:
>> Hi all,
>>
>> looks like this one is related to a recent change in core john
>
> I worked around that segfault by repeating the first test case:
>
>
> diff --git a/src/NS_fmt_plug.c b/src/NS_fmt_plug.c
> index 864395d..3f3849b 100644
> --- a/src/NS_fmt_plug.c
> +++ b/src/NS_fmt_plug.c
> @@ -58,6 +58,7 @@
> static struct fmt_tests tests[] = {
> {"admin$nMjFM0rdC9iOc+xIFsGEm3LtAeGZhn", "password"},
> {"a$nMf9FkrCIgHGccRAxsBAwxBtDtPHfn", "netscreen"},
> + {"admin$nMjFM0rdC9iOc+xIFsGEm3LtAeGZhn", "password"},
> {NULL}
For a while, this workaround helped.
But some time later I got the same segfault for another format, when
running
$ valgrind --leak-check=full ./john --test=1 2>&1 | tee valgrind-lc-test
This time the segfault occurred when testing krb5.
That's why I reverted aab646b42afe93ca909ba1a99bc0e2a1b027a79d in my
local repository.
Frank
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.
