Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6947c30571009fcc291ccb6b213dd43e@smtp.hushmail.com>
Date: Wed, 29 May 2013 20:53:34 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Segfault - contest edition

On 29 May, 2013, at 19:19 , magnum <john.magnum@...hmail.com> wrote:
> On 27 May, 2013, at 14:24 , Guth <guth@...posor.com> wrote:
>> Hi,
>> I received a sig11 (from the github release used during contest) with the folowing CLI:
> ...
>> 4 proceses still run fine after segfault.
>> So my guess is segfault when wordlist length < fork_number
>> 
> 
> This is hopefully fixed now, thanks to Claudio.

I managed to sort-of reproduce the crash now, and the patch indeed fixes it. Well done Claudio, I did not even notice that there were OpenCL stuff in the back-trace (it wasn't even the OpenCL format running - the bug was that multiple calls were made to OpenCL destructors due to forking).

BTW, other issues reported during contest is either fixed or listed here:
https://github.com/magnumripper/JohnTheRipper/issues

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.