[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d2bdf5e162a10f0da7f4a1518232374@smtp.hushmail.com>
Date: Sun, 16 Aug 2015 19:51:04 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: phpass on CPU, aka dynamic_17
On 2015-08-16 19:44, Solar Designer wrote:
> On Sun, Aug 16, 2015 at 12:36:16PM -0500, jfoug@....net wrote:
>> On Sun, 16 Aug 2015 12:13:15 -0500, Solar Designer <solar@...nwall.com> wrote:
>>> Maybe we should simply (re-)create a separate phpass format
>>
>> This is probably the correct way to proceed, and make sure that format can
>> also prepare/split any $dynamic_17$ back into it's native hash type.
>
> OK, who is to work on it? magnum? Lei?
>
> Would recovering the old phpass format (pre-dynamic) make sense, to use
> it as a base for the new one?
Apparently that format pre-dates our git history so we need to get it
from whatever latest jumbo tarball had it (or just rewrite it).
I'll open a GitHub issue for it.
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.
