[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51849A60.4050000@mccme.ru>
Date: Sat, 04 May 2013 09:19:28 +0400
From: Alexander Cherepanov <cherepan@...me.ru>
To: john-dev@...ts.openwall.com
Subject: Re: Paths rework
On 2013-05-01 18:23, D A wrote:
> The "run" directory in JTR-jumbo is a mess, so I tidied it up a bit.
What's the problem with run/ dir?
> The first commit simply moves around some files already present in
> run/, while the others fixes the paths in the Makefile.
> The dfb3c5f commit fixes the path of john.exe in symlink.c.
> I've been able to test only the linux-x86-64 build (and everything
> worked fine there).
> The charsets have been moved to $JOHN/run/charsets and their paths
> have been modified accordingly in john.conf
If you want to move some files to another dir why make it subdir?
$JOHN/charsets/ seems better.
> The dumb32.conf, dumb16.conf and dynamic.conf config files have been
> moved to $JOHN/run/configs and their paths have been modified
> accordingly in john.conf
> Everything in charge of converting a fileformat to a john-compatible
> format has been moved to $JOHN/run/xyz2john
> The others misc utils and scripts have been moved to $JOHN/run/utils
Having 3 distinct dirs with executables doesn't seem very useful to me.
> I am working on the bleeding-jumbo branch to be sure to catch every new commit.
> Magnum suggested to discuss these changes on john-dev, so here I am :)
--
Alexander Cherepanov
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.
