Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0bf322279753928702391a527a1750e3@smtp.hushmail.com>
Date: Fri, 6 Sep 2013 23:07:09 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Problem with Session restore

That's very odd. There was a bug like that and it was fixed half a year ago or more. Try this:

./john --restore:john

or

cd ../src ; ../run/john --restore:../run/john

just in case you get a difference. FWIW I did try your exact input file and .rec file and they resumed just fine after I fixed that bug in commit d10e869. I have absolutely no idea why you get problems I did not experience.

magnum


On 6 sep 2013, at 17:37, Marc Brinkmann <marc.brinkmann@...il.com> wrote:

> sorry, doesn't work for me :o
> i just pulled, compiled (clean linux-86-64-native) and then tried to resume:
> ~/JohnTheRipper/run$ ./john --restore
> fopen: $JOHN/john.ini: No such file or directory
> 
> 
> 
> 
> 2013/9/6 magnum <john.magnum@...hmail.com>
> 
>> On 6 sep 2013, at 14:47, I wrote:
>>> If it doesn't say 1.7.9-jumbo-8-RC, you did something wrong when
>> checking it out from git. See http://openwall.info/wiki/john/patches
>> 
>> I now found the bug. One pesky little bugfix that was made to the
>> bleeding-jumbo branch had never made it into unstable-jumbo (that you use,
>> and must keep using in order to resume).
>> 
>> Pull latest changes and you should be able to resume your file (I can).
>> 
>> Thanks for finding this problem!
>> 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.