[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0b8bbe9ae2b8902ba7bd19a615b8e049@smtp.hushmail.com>
Date: Sun, 05 Jul 2015 23:23:30 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: more robustness
On 2015-07-05 16:29, Frank Dittrich wrote:
> On 07/05/2015 03:34 PM, Solar Designer wrote:al cracking runs.
>>> But the name --fuzz-dump would collide with --fuzz, wouldn't it?
>>
>> I hope the current option parsing code would handle this fine, requiring
>> that --fuzz be spelled in full. If not, the code needs to be enhanced.
>
> I should have checked it before posting.
> At least bleeding-jumbo handles this situation, tested with the
> --prince[=FILE] option.
> If --prince is abbreviated, it collides with all the --prince-* option
> names, but --prince or --prince=file are accepted.
There's just one little detail to get right if having both --fuzz and
--fuzz-dump: You need to declare the shortest one first. For example,
the --prince option is at line 73 of options.c and the sub-options are
beneath it.
Our bash completion also handles it, after some tweaking when we
introduced the prince options.
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.
