Date: Wed, 8 May 2013 00:32:43 +0400 From: Solar Designer <solar@...nwall.com> To: Tavis Ormandy <taviso@...xchg8b.com> Cc: john-dev@...ts.openwall.com Subject: Re: --fork On Wed, May 08, 2013 at 12:26:34AM +0400, Solar Designer wrote: > Unfortunately, this does mean that some future versions will need to > support both approaches for a while (the approach currently implemented > for 1.8 will still be needed for restored sessions). I think I'll > increase "compat" from 2 to 3 along with making the change, and some > versions of JtR will need to support both 2 and 3 in restored sessions > for a while. BTW, another thing in inc.c that I intend to revise after 1.8 is the expand() logic. I think it is possible to improve incremental mode's efficiency (in terms of passwords cracked per candidates tested) by doing the expand()s smarter. I just did not have time to do the necessary testing in time for 1.8. So we have this other reason to break compatibility post-1.8 anyway. Ideally, we'd break compatibility just once for both of these changes, although this will again depend on how much time I have for this before a further JtR release. 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.