|
Message-ID: <BLU0-SMTP346EE5FA8E3D86FE0121177FD100@phx.gbl> Date: Tue, 8 May 2012 22:31:10 +0200 From: Frank Dittrich <frank_dittrich@...mail.com> To: john-dev@...ts.openwall.com Subject: Re: Fwd: bash auto-completion for john On 05/08/2012 08:15 PM, Frank Dittrich wrote: > For --wordlist=*|--config=*|--pot=*|--make-charset=*, I still list all > matching files and directories (in the current directory, unless the > value on the command line already includes path information). > I'm still thinking about removing the expansion for --make-charset=. > For --pot= and --config=, the list should probably filtered (just > directory names and *.pot or *.conf/*.ini files). > > Still not working: correct handling of file names starting with ~. Expansion for --wordlist=~/test or --wordlist=~fd/test now works ./john --wordlist=~/te now gets expanded to ./john --wordlist=/home/fd/test.txt when I press the tab key. This is how this section now looks like: --wordlist=*|--config=*|--pot=*|--make-charset=*) #cur=${cur#*=} #_filedir doesn't work for --wordlist=~/te # _filedir_xspec "_xspecs: bad array subscript" written to stderr _filedir_xspec 2> /dev/null return 0 ;; Since this still only helps when pressing the tab key on the command line, would it be a good idea to do the tilde expansion from within john? Apparently, wordexp or glob could be used for tilde expansion. I still don't know why this works on Stephen John Smoogen's system: $ john --session=DD --wordlist=~/x --pot=xyz.pot --format=raw-md5 y000 Loaded 10 password hashes with no different salts (Raw MD5 [SSE2i 10x4x3]) guesses: 0/80 time: 0:00:00:00 DONE (2012-05-06 14:51) c/s: 285 trying: redhat - rhel This suggests an RHEL system: $ rpm -q bash john bash-4.1.2-8.el6.x86_64 john-1.7.9-1jumbo5.el6.x86_64 see Message-ID: <CANnLRdgDWBDVRfjfB6LRJGDdU-w5-OU3kMEqQsDkJoJvKWLZQA@...l.gmail.com> or http://openwall.com/lists/john-users/2012/05/06/3 Frank
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.