[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a48bade312b0cf9140795afb2d71d496@smtp.hushmail.com>
Date: Tue, 27 Aug 2013 01:32:39 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Sayantan Weekly Report #11
On 26 Aug, 2013, at 23:07 , magnum <john.magnum@...hmail.com> wrote:
> Just thinking out loud, I wonder how we want to [eventually] fix the status line candidate output. I think the current aazzvpo..aazzvpo should be either aazzvpo..zzzzvpo or a single **zzvpo. For some masks it's really confusing now:
No, wait. It should be aazzvpo..zzzzzzz, right? I presume "aa" is from GPU generation and "zzvpo" is from mask.c and neither is correct for the final candidate (we did run to completion).
So it should be either zzzzzzz, **zzzzz or perhaps *******.
As long as get_key() does what it should (and otherwise we'd have false cracks) I guess we need a fix in crk_get_key2(). Maybe this will be easily solved with the upcoming num_internal_keys you mentioned.
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.
