Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4D93A4A7.9030204@bredband.net>
Date: Wed, 30 Mar 2011 23:46:15 +0200
From: magnum <rawsmooth@...dband.net>
To: john-users@...ts.openwall.com
Subject: 1.7.7 Incremental (was Re: Replacement for all.chr based
 on "Rock You" Passwords. URL inside.)

On 2010-02-05 02:50, Solar Designer wrote:
> I already have some test revisions of charset.c and inc.c files that
> address one of the shortcomings of the current approach (namely, its
> inability to increase the number of character indices for each character
> position fully independently from the rest of the positions).  Even if I
> maintain support for older .chr files for a while longer (with some
> backwards compatibility code), it'd be beneficial to take advantage of
> the new approach and implementation.

I would love this and other major enhancements to Incremental...

And even longer ago, on Sun, 11 Jan 2009, Solar Designer wrote:
> Actually, I regret not upping the compile-time setting to 9 shortly
> before the 1.7 release.  I should have probably done that as I
> re-generated the .chr files at the time anyway.  I did not have to
> actually include data for length 9, but having the compile-time limit
> set higher would allow for my bundled .chr files to co-exist with files
> that JtR users could generate themselves for length 9.

...but I would appreciate this in the meantime. Is there a reason not to 
do it for 1.7.7? Does it have to be at a major version bump? Or is just 
that the charset re-generation would take a lot of of your time?

cheers
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.