[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 18 Feb 2012 18:48:57 +0100
From: Samuele Giovanni Tonon <samu@...uxasylum.net>
To: john-dev@...ts.openwall.com
Subject: Re: format names for GPU-enabled implementations
On 02/18/12 17:41, Solar Designer wrote:
> On Sat, Feb 18, 2012 at 05:36:23PM +0100, magnum wrote:
>> On 02/18/2012 05:08 PM, Solar Designer wrote:
>>> We'd need to have "john" print something at runtime as well when it
>>> has GPU code in it, is invoked on a GPU-enabled hash type, but
>>> without the proper --format option (so using the CPU only). %-)
>>
>> This is already the case!
>>
>> magnum@...ge:john$ ./john test/test.md5
>> Warning: detected hash type "md5", but the string is also recognized as
>> "cuda-cryptmd5"
>> Use the "--format=cuda-cryptmd5" option to force loading these as that
>> type instead
>> Loaded 4 password hashes with 2 different salts (FreeBSD MD5 [SSE2i 12x])
>> Remaining 2 password hashes with no different salts
>
> Oh, indeed. :-) Since this code was put in for a different purpose
> (ambiguous hash encodings), somehow I did not realize it'd do just what
> we need here - but indeed it does. Thanks!
>
> OK, let's keep things as they are, then.
also, since opencl formats are registered in john.c
with a define we could add them
before the
cnt = dynamic_Register_formats(&pFmts);
in that way they become the default for that given format .
i don't know if it mess up with cpu formats.
btw i'm a bit unfamiliar with cuda but i think we can't merge them:
cuda is nvidia only therefore on nvidia cards it would compile but
that's not possible on ati .
about documentation there's a Redme.opencl on the doc dir, which is
something i did in the spare time.
unfortunately i'm still a noob with git and pull requeste so i will add
it here for simplicity
Cheers
Samuele
View attachment "README.opencl" of type "text/plain" (3826 bytes)
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.
