john-users - Re: bash auto-completion for john (Was: file name expansion for --wordlist= and file name starting with ~)

Openwall wordlists collection for password cracking (20+ languages)

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Mon, 7 May 2012 11:31:20 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-users@...ts.openwall.com
Subject: Re: bash auto-completion for john (Was: file name expansion
 for --wordlist= and file name starting with ~)

On 05/07/2012 10:42 AM, Frank Dittrich wrote:
> For all these cases
> $ vim -d:~/test
> $ vim --dummy:~/test
> $ vim -d=~/test
> $ vim --dummy:~/test
> I can press the tab key, and the file name gets expanded to
> /home/fd/test.txt
> 
> But the same doesn't work for ./john.
> It doesn't work for or john /usr/bin/john, either. I just installed
> fedora's package to test this.

After
$ complete -F _filedir_xspec john

I can use tab completion here
$ john --wordlist=~/test
and it gets expanded to
$ john --wordlist=/home/fd/test.txt

This doesn't just work for john (/usr/bin/john), but also for ./john (in
the run subdirectory of my user's local john installation.).

To make this work permanently, I included the following line into my
~/.bashrc:
complete -F _filedir_xspec john

Should I dig into bash auto-completion even more, to support expanding
--wo to --wordlist= and so on?

What other john-specific auto-completion would be useful?
(Doing this correctly for all possible cases will probably be hard.
Jumbo supports an extended set of options. Different shells might have
different auto-completion mechanisms. Some distributions might already
provide auto-completion logic for john.)

Frank