[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e4ec3f80b0117096d187c854b6f0ba95@smtp.hushmail.com>
Date: Fri, 11 May 2012 10:00:43 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Fwd: bash auto-completion for john
On 05/11/2012 02:04 AM, Frank Dittrich wrote:
>> Now, I look forward to some more bash completion magic from Frank!
>
> May be I'll not be able to work on this tomorrow. We'll see.
> But it shouldn't be too hard for you to extend the current logic.
I committed a first version using this. I believe there was a bug in
original line #163 - should there not be a %=* in that?
--rules|--single)
- if echo "${valopts}" | grep "^${cur}$" >
/dev/null ; then
+ if echo "${valopts}" | grep "^${cur%=*}$" >
/dev/null ; then
- COMPREPLY=( $(compgen -W "${cur}
${cur}=NT ${cur}=single ${cur}=wordlist" -- ${cur}) )
...
My version always lists all external modes. It will be tricky to decide
when to only list filters/modes. Or maybe not always? If we do not know,
we list all. If another cracking mode is already present, we list only
filters. Anyway, I will not do any more than this.
BTW I also committed this:
$ ../run/john --list=hidden-options
--list=NAME list configuration, rules, etc
--mkpc=N force a lower max. keys per crypt
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.
