[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d34bbfe01dc800acad4f0ca1982b2344@smtp.hushmail.com>
Date: Mon, 07 May 2012 19:54:37 +0200
From: magnum <john.magnum@...hmail.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 11:31 AM, Frank Dittrich wrote:
> Should I dig into bash auto-completion even more, to support expanding
> --wo to --wordlist= and so on?
This has been on the wiki wishlist for quite some time. But doing it
"properly" is not a one beer job.
> 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.)
An excellent example of advanced autocompletion is git. If I write "git
checkout j" and hit tab twice, it will list branches starting with j.
Behind the scenes, it actually queried the repos in real time (and
probably caches results too).
So an ideal implementation for john IMO would be, for example, --rules=
auto-completing with a list of your currently available rules. And
--external= would auto-complete with a list of currently available
external modes/filters. From your own very john.conf, and including
sub-conf-files sourced with the .include directive... this could start
out much simpler than this but the possibilities are endless!
magnum
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.
