[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <07da4cc12e5c8a00b3063534262bec05@smtp.hushmail.com>
Date: Fri, 23 Nov 2012 09:40:12 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: "Hide" more options
On 11/23/2012 12:28 AM, Frank Dittrich wrote:
> One option remained in the main usage output, but I think it should also
> be moved to --hidden-options:
> --plugin=NAME[,..] load this (these) dynamic plugin(s)
Yes, that was just me being lazy with keeping track of the ifdefs.
> IMHO, there are even more options which could/should be moved from the
> main usage output to the output of --list=hidden-options:
>
> --pipe like --stdin, but bulk reads, and allows rules
> --loopback[=FILE] like --wordlist, but fetch words from a .pot file
> --dupe-suppression suppress all dupes in wordlist (and force preload)
> --encoding=NAME input data is non-ascii (eg. UTF-8, ISO-8859-1).
> For a full list of NAME use --list=encodings
> --pot=NAME pot file to use
IMHO we should only move --plugin. My main concern was super-rarely-used
options, debug/test options and stuff that was placed below the format list.
> The following option should be moved above the --format=NAME line
> (similar to the core john version).
Did you miss to include something here?
> If we really move that many option to --list=hidden-options, the
> --list=WHAT description might need to get a little bit longer (and I
> think it should stay at the end of the usage output). What about this:
>
> --list=WHAT list capabilities, see --list=help or doc/OPTIONS,
> see --list=hidden-options for more options
Agreed.
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.
