[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Feb 2012 04:07:47 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: generic crypt [was: OpenCL support on OSX]
On Wed, Feb 01, 2012 at 09:04:28AM +0100, magnum wrote:
> Nevermind. But speaking of crypt, I now noticed that FreeBSD et al do
> not use c3_fmt. Is that because they would probably not give us any new
> format?
That was my original rationale, yes - but it no longer applies. FreeBSD
now supports Ulrich's SHA-crypt (at least I see it in their source tree).
> It could still be usable for verifying MD5's for longer than 15
> chars, and such things. And they may introduce new stuff, just like
> DragonFly BSD.
Right. Perhaps we should enable c3_fmt for more systems. And your
proposal is actually a good one in that context.
We could also enhance c3_fmt itself to detect salts for DragonFly's
broken SHA-2 stuff (now obsoleted due to our pushing).
> BTW it seems OSX do have a crypt(3) capable of original DES and the one
> with _salt (From memory that's BSDI, right?). Would it not work with
> HAVE_CRYPT?
I think it would work. Do you know if it supports anything else as well?
> Not that it would add anything useful to John, except
> showing how much faster optimised bitslice DES is compared to crypt calls :)
Right.
Alexander
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.
