[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <FE11C1AF-0EAB-4809-9F69-B43BCEBB4ABC@patpro.net>
Date: Fri, 7 Aug 2015 09:57:58 +0200
From: patpro@...pro.net
To: john-users@...ts.openwall.com
Subject: Re: Benchmark result
Hello,
>> ./john --fork=8 --device=0,1,2,3,4,5,6,7 --format=Raw-SHA256-opencl
>
> This is a total waste of GPUs. Don't do it. For fast hashes (anything
> starting with raw-*, some others), we generally don't have efficient
> code on GPUs, with some recent exceptions (Sayantan has implemented mask
> mode on GPU recently, for a handful of fast hash types, but not for all).
>
> So if you want to crack fast hashes on GPU, please make sure your
> specific hash type has mask mode on GPU and then do use mask mode (maybe
> in combination with wordlist or incremental mode).
That's a very interesting information. I'm only using JtR once in a while and I don't have a deep knowledge of its behavior/optimizations. Is there any up-to-date table that would lists hashes/ciphers with their most efficient cracking device (being either CPU or GPU) ?
regards,
pat
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.
