[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP34841602202023A5B1DC2D8FD100@phx.gbl>
Date: Tue, 8 May 2012 11:24:03 +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:11 AM, magnum wrote:
> On 05/08/2012 02:27 AM, Frank Dittrich wrote:
>> Proper bash completion support for john needs much more effort.
>>
>> But here is a first humble attempt to support expansion of option names
>> and expansion of file names for options --wordlist=, --config=, --pot=,
>> and --make-charset= (the last option probably should be ignored, to make
>> accidentally overwriting files harder).
Arrgh. I realized that with the current version, options with file names
starting with a tilde don't work as expected.
> BTW for easier implementation of dynamic completion we could add hidden
> options to john. For example, "john --list-rules" and "john
> --list-ext-modes". This would make realtime loading easier,
> automatically following .include directives and so on. It should also
> support "john --conf=other.conf --list-rules".
Good idea. We should, however, try to use just one option instead.
E.g., --list=rules, --list=ext-modes...
> I suppose we should add a make target that just copies src/bash to
> /etc/bash_completion.d/ and mention this in some documentation file.
The user would need write permission for /etc/bash_completion.d/.
For a system-wide installation, this is probably OK.
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.
