[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <295df4875e8a38d4781e2a1e40ff8194@smtp.hushmail.com>
Date: Thu, 09 Apr 2015 18:34:26 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: [GSoC] John the Ripper support for PHC finalists
On 2015-04-09 18:13, Solar Designer wrote:
> On Thu, Apr 09, 2015 at 03:33:03AM -1000, Agnieszka Bielec wrote:
>> opencl version using private memory is in private_memory branch,
>> the older version of private memory also is in bleeding-jumbo and
>> there is also a global memory version in older commit
>> I will be working on bleeding-jumbo
>
> I leave it up to magnum to decide how/when this code should be getting
> into bleeding-jumbo.
We can merge it to bleeding at any time, just send a pull request on
GitHub. I'm fine with it being WIP as long as it doesn't break anything.
For example, if it fails self-test in some cases that would be OK, but
if it crashes (aborting a full --test run) on some devices (eg. very
weak ones), it's not good and I will like it to be fixed. OTOH we could
just soft-disable it in john.conf in case we need to.
> Is your opencl_pomelo_fmt_plug.c still based on
> opencl_mysqlsha1_fmt_plug.c? (Sorry, I haven't looked at your latest
> yet.) I think you might want to re-do it in a cleaner way, based on a
> more appropriate format for a slow hash. magnum - any suggestions?
md5crypt (opencl_cryptmd5_fmt_plug.c) would be an excellent base for a
single-kernel format. Is there any chance Pomelo would benefit from a
split/loop kernel?
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.
