[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56D75A5F.6060100@mailbox.org>
Date: Wed, 2 Mar 2016 22:25:51 +0100
From: Frank Dittrich <frank.dittrich@...lbox.org>
To: john-users@...ts.openwall.com
Subject: Re: Reverse T9 rule
On 03/02/2016 09:44 PM, magnum wrote:
> Here's where I cowardly gave up:
>
> # Should do 624686 -> magnum (among many alternatives)
> [List.Rules:9T]
> s2[abc] s3[def] s4[ghi] s5[jkl] s6[mno] s7[pqrs] s8[tuv] s9[wxyz]
> s0[ ] Q
>
> The problem with this rule as written here is that given the input of
> 624686 it will replace *all* instances of "6" with either "m", "n" or
> "o". So it will produce candidates like magmum or nagnun but never
> magnum. Thus here's the challenge: Write a rule that actually works, as
> efficiently as possible. Can it be accommplished at all? Perhaps we'd
> need a new rule command?
I'm afraid a completely generic solution just with --rules isn't possible.
I think you'll need rexgen support and define a new regex alphabet you
can use with --regex.
Alternatively, enhance --external to support generating multiple
candidates per input word, and define a new external mode.
Frank
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.
