[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150507144635.GB12485@openwall.com>
Date: Thu, 7 May 2015 17:46:35 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: Session names somename.[0-9]+ shouldn't be allowed
On Wed, May 06, 2015 at 11:57:11PM +0200, 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:
> >> 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.
[...]
> 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/.
>
> So, dots in the path name should be allowed.
Ouch. I'd rather not. As I just wrote in another message, this was
never supposed to work that way. The option specifies session names,
not pathnames.
However, I am open to discussing and possibly changing this, if there
are good reasons to allow for pathnames there.
Alexander
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.
