Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 18 Feb 2012 20:41:44 +0400
From: Solar Designer <>
Subject: Re: format names for GPU-enabled implementations

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!
>$ ./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.


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.