|
Message-ID: <20170818132658.GB19067@openwall.com> Date: Fri, 18 Aug 2017 15:26:58 +0200 From: Solar Designer <solar@...nwall.com> To: john-users@...ts.openwall.com Subject: Re: Not understanding why rule is not working On Fri, Aug 18, 2017 at 03:09:36PM +0200, Virginie trinite wrote: > I try to retrieve a password of mine, for which I do not remember where I > put the uppercase. > I find this interesting rules, which do what I want but only for the first > 14 characters, and my password is very long. > > [List.Rules:NT] > l > lMT[*0]T[*1]T[*2]T[*3]T[*4]T[*5]T[*6]T[*7]T[*8]T[*9]T[*A]T[*B]T[*C]T[*D]Q > > I try to extend it, but as soon as I arrive to G, it doesn't work anymore. > As variable G has nothing specific, I wonder where is the problem > > [List.Rules:NT] > l > lMT[*0]T[*1]T[*2]T[*3]T[*4]T[*5]T[*6]T[*7]T[*8]T[*9]T[*A]T[*B]T[*C]T[*D]T[*E]T[*F]T[*G]Q > > It says Invalid rule in ./john.conf at line 631: Invalid position code You're bumping into this limit in params.h: /* * Maximum number of character ranges for rules. */ #define RULE_RANGES_MAX 16 You can raise it and recompile. And given your reasonable use case, maybe we need to raise the default for this parameter, say, to 30. Maybe we also need to report an error when this limit is hit, instead of silently not performing the preprocessor expansion (which results in confusing error messages from further processing, like you have seen). Also related: JtR performs preprocessor expansion of the rules at startup, to count the expanded rules (such as for progress reporting) and validate their syntax. With extreme use of the preprocessor like this, JtR startup may be slow. Too many expanded rules may also overflow the integer variables (but your specific use is safe in this respect, as long as you don't go beyond 30 preprocessor expansions). Alexander
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.