[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <295517fdc275553a1b7b361731b179f7@smtp.hushmail.com>
Date: Tue, 10 Dec 2013 16:53:27 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: md5crypt-opencl
On 2013-12-10 09:07, Frank Dittrich wrote:
> On 12/10/2013 01:42 AM, magnum wrote:
>> No wait... maybe it isn't that complicated. Actually, core calls
>> set_key() and then forgets all about that key - the *format* is
>> responsible for recalling that key when needed. So in theory, we could
>> wait for hours filling a particular seldom-used-length if we really
>> wanted to. And/or we can re-order keys however we want (except the
>> current self-tests will get mad about it so we'd need to fix that). This
>> never occured to me until now.
>
> But what happens with interrupted / restarted sessions?
> Will you complete all the partly filled buckets before terminating the
> session?
> Will a restarted session repeat much of the work that has already been
> done before?
> Will you silently drop candidates?
That must be taken care of. Silently dropping a candidate is never
acceptable. It's as bad as any false negative.
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.
