[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8192a058f7d0aece36b111c2f032e852@smtp.hushmail.com>
Date: Sat, 9 Feb 2013 15:54:24 +0100
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Support for PBKDF2 (SHA512)
On 9 Feb, 2013, at 15:41 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
> On Sat, Feb 9, 2013 at 7:28 PM, magnum <john.magnum@...hmail.com> wrote:
>> I'm implementing support for $ml$ format with '.' delimiter. From what I can google, a grub hash looks like this:
>>
>> grub.pbkdf2.sha512.10000.4483972AD2C52E1F590B3E2260795FDA9CA0B07B96FF492814CA9775F08C4B59CD1707F10B269E09B61B1E2D11729BCA8D62B7827B25B093EC58C4C1EAC23137.DF4FCB5DD91340D6D31E33423E4210AD47C7A4DF9FA16F401663BF288C20BF973530866178FE6D134256E4DBEFBD984B652332EED3ACAED834FEA7B73CAE851D
>>
>> So what format *do* we support? Why do we use a '$' delimiter? Can I drop that?
>
> The current ml2john.py program produces hashes starting in
> $pbkdf2-hmac-sha512$ and it uses '.' delimiter.
Then it did not work until now. The format only supported '$' delimiter.
> This change was done after multiple rounds of discussions with other developers.
>
> IIRC in the past, we used to produce hashes starting with $ml$ with
> '$' as the delimiter. I had no idea that an external tool had adopted
> our "old-style" / development hash format.
We did not invent that. The "dave" tool is older than us (I think).
Anyway, I have code that supports any of these three tags as well as any delimiter of '.' or '$'. I'll commit it after some more testing.
BTW I also fixed bogus stuff in valid vs binary/salt. We should catch bad input in valid(), not later.
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.
