[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120508071131.GA24873@debian>
Date: Tue, 8 May 2012 11:11:31 +0400
From: Aleksey Cherepanov <aleksey.4erepanov@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Fwd: bash auto-completion for john
On Tue, May 08, 2012 at 08:11:25AM +0200, 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).
>
> Great, I'll try it out. This will be very convenient as-is, especially
> for new users that don't remember all options.
>
> I suppose an intermediate step towards perfection could be to hard-code
> rules and external modes that are included in JtR per default.
>
> 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".
Such option would be useful for Johnny the GUI too. It seems to be perfect to
keep such functionality in John itself and do not implement it again in every
wrapper.
Regards,
Aleksey 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.
