Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 17 Jul 2012 11:15:10 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: fopen: john.rec: No such file or directory

On 07/16/2012 12:05 AM, magnum wrote:
> On 2012-04-20 13:05, magnum wrote:
>> Using core JtR, I can run a session from src directory, stop the job,
>> and resume just using "../run/john -res"
>>
>> But using released Jumbo-5 or latest git, this does not work, I get
>> "fopen: john.rec: No such file or directory". A workaround is adding the
>> session file path "../run/john -res:../run/john".
> 
> Bump. This has been brought up on john-users too now. Could someone have
> a look at the 1.7.9-jumbo-6-fixes branch and try to nail this? Note that
> the bug was present in Jumbo-5 already, possibly even earlier.

The error is already present in john-1.7.9-jumbo-3.
(jumbo-1 and jumbo-2 are not tagged. Even if they were, I suspect the
majority of changes came with jumbo-1.)

When looking at the changes in path.c, it looks like magnum is to blame:
$ git blame path.c|cut -d" " -f 1-2|sort|uniq -c
     25 1171931f (solar
     97 ^ad53c2d (solar
     70 de989e6e (magnum
      2 df1b4729 (solar

But of course, those 70 lines could have come from patches created by
others, and magnum was just the one who integrated those patches into jumbo.

git blame also shows 69 de989e6e lines for recovery.c, 239 for john.c
(+5 8d9f3ad8 lines, definitely unrelated) and 299 for options.c (+2
23d70dc5 lines, unrelated).

commit de989e6e12f48090f1b3dd095ea327ed8a2df30e
Author: magnum <magnum>
Date:   Wed Nov 9 12:20:47 2011 +0100

john-1.7.9-jumbo-1 (1.7.8-jumbo-8 equivalent)

Anybody out there who still has a 1.7.8-jumbo-8 build and sources?
Unfortunately, I have no more time right now.

Frank

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ