Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120622021324.GA28345@openwall.com>
Date: Fri, 22 Jun 2012 06:13:24 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: cuda format names

On Fri, Jun 22, 2012 at 03:48:35AM +0200, Lukas Odzioba wrote:
> Someone changed cuda format names (phpass + crypt*)

I did, as discussed in here.

> 0) I am assuming that it is because naming consistency - for the same
> reason I was changing *crypt to crypt* almost year ago...

Yes.  phk recently made it fairly clear that it's md5crypt, and he is
the authoritative source. ;-)

> 1)  phpass-opencl :) in cuda build

That's a bug (probably mine).  Please fix it.

> 2) we do not have md5crypt cpu build, so I thing it should be
> crypt-cuda rather than cryptmd5-cuda

Huh?  I am puzzled by your logic here.  Let's use md5crypt-cuda and
md5crypt-opencl as we currently do.  As discussed, md5 may also be
renamed to md5crypt - but in core JtR tree for 1.8 - not right now.

> 3) do we want to change file names or we leave them as they're now
> (crypt*_fmt.c)?

Let's leave them as they are for now and revisit this later,

Thanks,

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.