Date: Thu, 2 May 2013 03:12:53 +0200 From: magnum <john.magnum@...hmail.com> To: john-dev@...ts.openwall.com Subject: Re: Paths rework On 1 May, 2013, at 16:23 , D A <lupo996@...il.com> wrote: > Straight C&P from my pull request on GitHub: > > The "run" directory in JTR-jumbo is a mess, so I tidied it up a bit. > 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 This sounds reasonable to me, with the slight caveat that it diverges from core (unless Solar does the same for 1.8 of course). > 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 This might be a good idea too, and is not applicable to core. > 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 This could pose a problem for JOHN_SYSTEMWIDE builds. And it has the disadvantage that if you want John & co. in your path, there are now three directories to add. Personally I don't put it in my path but I'm used to supply the path or work from the run directory (so "./john"). Having to use three different paths will be a nuisance, at least 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 :) Yes, so what does everyone think? 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.