Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 5 Jun 2012 19:40:37 +0200
From: Frank Dittrich <>
Subject: Re: Do we need --list=formats?

On 06/05/2012 09:53 AM, magnum wrote:
> Done. BTW the bash completion doesn't seem to complete further than
> --list= right now, I think it did earlier?
> magnum

IMO it works as designed.

For a john version which doesn't know --list, it does nothing.

For a jumbo version:

$ ./john -l[tab]
$ ./john --list=

$ ./john --list=[tab][tab]
lists these completions:
?                 ext-filters-only  hidden-options
build-info        ext-modes         inc-modes
ext-filters       externals         rules

$ ./john --list=?[tab]
just adds a space after the '?'.

$ ./john --list=b[tab]
$ ./john --list=build-info

$ ./john -l:r[tab]
$ ./john -l:rules

$ ./john -l=e[tab]
$ ./john -l=ext

$ ./john -l=ext[tab][tab]
lists these possible completions.

ext-filters       ext-modes
ext-filters-only  externals

What john version are you using?
Can you post the output of

$ ./john --list=?

$ ./john --list=build-info

$ echo "_${__john_completion}_"

$ echo "_${COMP_WORDBREAKS}_"

Do I have to fetch the latest git version to reproduce?


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.