Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d04f40371a5a6033d6242db4e59b002d@smtp.hushmail.com>
Date: Tue, 30 Apr 2013 10:44:24 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Node support

On 30 Apr, 2013, at 3:21 , Solar Designer <solar@...nwall.com> wrote:
> On Mon, Apr 29, 2013 at 08:20:12PM +0200, magnum wrote:
>> OK I now understand what happens. It's because of my uneven splitting (sometimes I play clever). The code is wrong for the case I used, ie:
>> 
>> Session A running 1-3/7
>> Session B running 4/7
>> Session C running 5-6/7
>> Session D running 7/7
> 
> Oops.  I managed to introduce a severe design error when making some
> optimizations.  This is now corrected.  Thank you!

Now node 1/n loads first 1/n consecutive words. This is suboptimal if wordlist is sorted "best first", or by length. OTOH it might sometimes result in better dupe suppression after applying rules.

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.