|
Message-ID: <518702F8.4030009@mccme.ru> Date: Mon, 06 May 2013 05:10:16 +0400 From: Alexander Cherepanov <cherepan@...me.ru> To: john-dev@...ts.openwall.com Subject: Re: Paths rework On 2013-05-04 16:33, jfoug@....net wrote: > However, if we are proposing changes, then how about: > > 1. make $JOHN be the base directory of john, (under .current /src and ./run) > 2. place john.conf into this dir (i.e. base dir, the new $JOHN). How this dir is determined? Can john be placed in ~/bin? Does it play well with system-wide install? Maybe it's worth it to have real install target in Makefile and install john into /opt? > 3. add a new section to john.conf, that sets required location information for all other items. > 4. place all executable files in 1 directory. Whether it is run or bin, I do not care, but convention is bin. > 5. make whatever changes are required in john executable or any other supporting executable to make sure they honor this. > 6. if partial path file names are given on command line (i.e -pot=jims.pot -wo:mybig_list.dict), then john would search in the dir listed in the john.conf section. I agree with Frank that there is a problem with current dir. One way is to have a list of dirs in config instead of one dir. Like this: chr_dir = .:$JOHN/charsets Another way is to do it implicitly. > 7. have a env var JOHN_LOCAL_CONF_DIR, and have john and other 'tools' honor that. In fact the bottom local file include could be .include "$JOHN_LOCAL_CONF_DIR/john.local.conf" If JOHN_LOCAL_CONF_DIR is not set in env, then JOHN_LOCAL_CONF_DIR would fallback to $JOHN > > [Options:Locations] > wordlist_dir = $JOHN/wordlists > rec_dir = $JOHN/tmp > log_dir = $JOHN/tmp > pot_dir = $JOHN/cracks > exec_dir = $john/run (or $JOHN/bin) > chr_dir = $JOHN/charsets > stats_dir = $JOHN/charsets -- 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.