[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f5ccc792c53b5ee57ed4982caa1657bd@smtp.hushmail.com>
Date: Thu, 07 May 2015 01:12:19 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Session names somename.[0-9]+ shouldn't be allowed
On 2015-05-06 23:57, Frank Dittrich wrote:
> On 05/06/2015 08:26 PM, Solar Designer wrote:
>> On Wed, May 06, 2015 at 06:21:14PM +0200, Frank Dittrich wrote:
>>> On 05/06/2015 05:58 PM, Solar Designer wrote:
>>>> "Disallow session names with dots since these clash with those produced by
>>>> --fork. Suggested by Frank Dittrich."
>>>>
>>>> http://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/packages/john/john/src/options.c.diff?r1=1.39;r2=1.40
>>>
>>> You don't even allow --session=test.md5crypt anymore.
>>
>> Yes. I'd rather not. Let's keep the dot reserved for filename suffixes
>> added by John.
>
> Even worse, this breaks the JtR test suite.
> The test suite is located in a test subdir at the same level as run and src.
> (master)test $ ../run/john -ses=./tst -pot=./tst.pot cisco8_tst.in
> --wordlist=pw-70.dic -form=pbkdf2-hmac-sha256
> Invalid session name: must not contain a dot
>
>
> In this case, jtrts.pl uses --session=./tst to make sure the .rec and
> .log files remain in the test subdir, even if the john binary is located
> in ../run/.
They would anyway (I just verified it). Only un-named sessions end up in
the $JOHN directory. I never understood why Jim put "./" before the names.
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.
