[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABob6ioaJug+murWAK8KeTU1WE0knxtva2gVTJ3QBXiXPQtkRw@mail.gmail.com>
Date: Fri, 22 Jun 2012 04:18:30 +0200
From: Lukas Odzioba <lukas.odzioba@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: cuda format names
2012/6/22 Solar Designer <solar@...nwall.com>:
> 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.
No problem, I missed it.
>> 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. ;-)
Great.
>> 1) phpass-opencl :) in cuda build
>
> That's a bug (probably mine). Please fix it.
Ok
>> 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.
Not "build" i meant format name "crypt".
>> 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,
Ok
Lukas
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.
