[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <835783ab55caaae528e567dea49295e6@smtp.hushmail.com>
Date: Sat, 10 Jan 2015 06:40:29 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: PRINCE
On 2015-01-09 17:16, Solar Designer wrote:
> On Fri, Jan 09, 2015 at 05:02:02PM +0100, magnum wrote:
>> I saw a couple of bugfixes a day so far, so it's not completely stable.
>> We should try to keep it "mergable" in one way or the other. At least
>> refrain from large rewrites unless necessary. For example, we should
>> #ifdef out unneeded code blocks instead of dropping them.
>
> Right, or alternatively we reimplement and then maintain our own code,
> and submit it back to hashcat project. Maybe later. ;-) I think the
> dependency on GMP could/should be avoided, e.g. in favor of "double"
> (like our charset.c uses it) or in favor of saturation at 2^64-1.
Yes, later. We actually have a rough version committed now. It's Atom's
code used almost as-is, with the output prints replaced with
crk_process_key(). It does not yet support resume, node/fork or
ETA/progress but I will fix this in the nearest couple of days.
Performance is only half as good as I expected from something Atom
wrote. Maybe there's some really low hanging fruit, I haven't got to
that yet. My #1 prio is session save/restore, #2 is node/fork.
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.
