Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 28 Apr 2013 03:00:49 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: revised incremental mode and charset files

On 28 Apr, 2013, at 2:42 , magnum <john.magnum@...hmail.com> wrote:
>> I have some thoughts on the matter, but I have no time for a discussion
>> right now.  One of the aspects I am going to consider is download size
>> of the tarball that will include at least some of the .chr files for
>> which we provide john.conf sections.  For example, for all.chr or maybe
>> ascii.chr (hey, I independently thought of this name!), I may apply a
>> filter() which limits the length to 15 and charset to the 95 ASCII chars.
> 
> I'm not going to argue desperately against that but it has the downside that "upgraded" files will not be compatible (actually I'm not 100% sure: Will they?). I did think we could/should have a default MaxLen of lower than 24 but I'm not sure it's a good idea to limit the actual charset files. In Jumbo, we can over-ride MaxLen (in john-conf) with --max-len (command-line option). It's a pity you don't have that in core.

After another round of thoughts, and considering I agree. 15 is enough. The important thing is that params.h defaults to larger so the supplied files are not deemed unusable as soon as you create your own ones.

As for the number of files supplied, I don't care about core so we can have Jumbo include utf8.chr and ansi.chr while core just has all.chr (or ascii.chr). I see no problem with that.

magnum

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ