[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <267f07e3ac4505238cfe5b818d6c15c1@smtp.hushmail.com>
Date: Sat, 27 Apr 2013 14:36:59 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: revised incremental mode and charset files
On 27 Apr, 2013, at 12:16 , magnum <john.magnum@...hmail.com> wrote:
> I'm thinking we might want to do something like this:
> * all.chr is actually made with filter_ascii, to be more like the old one.
> * a new one, utf8.chr, is made with no filter (assuming pure junk was already removed/filtered, if we care about that).
> * and a new ansi.chr is made from same data as utf8, but converted to CP1252.
>
> With corresponding entries in john.conf, this will make some sense. --inc=utf8 and --inc:ansi are intuitive, and just -inc will be much like before (albeit with different training).
I added the mentioned chr files to bleeding for now, for easy testing.
-inc:all still has a MaxLen=8 in john.conf but it can be over-ridden with --max-length command line option.
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.
