[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8a03db049fa3bd31e500444d611576e2@smtp.hushmail.com>
Date: Sat, 12 Sep 2015 17:26:51 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: mask + external as filter, generic combinable filters
On 2015-09-12 17:15, Frank Dittrich wrote:
> On 09/12/2015 05:10 PM, magnum wrote:
>> Yes, currently when combining mask mode with external, external is the
>> generator and mask mode is an amplifier (eg. word -> word1, word2, word3).
>>
>> We should probably support the other way round too, eg. mask generator
>> and external filter. But what would the option syntax be for selecting
>> behavior? If nothing else, an external mode that lacks generate(), like
>> in your case, should automagically select mask mode as the generator.
>
> Yes, I think if external mode lacks a generate() function, mask mode is
> the generator.
> If external mode has a generate() function, the mask must contain either
> "?w" or "?W".
Oh right, that is a selection criteria already. So we should definitely
be a generator (and support an external filter) any time we don't have
\w or \W. And we can only be an amplifier when we have them. We need to
fix this.
> For --regex it would be similar. If the external mode has a generate()
> function, it is the generator, and --regex must contain "\0".
Not quite: Some external modes support being generator OR filter. So the
criteria is \0 only: If there is a \0, regex is the filter/amplifier and
otherwise it must be the generator.
BTW are we still supporting latest librexgen or did the API change again?
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.
