[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5027B4E2.5080103@linuxasylum.net>
Date: Sun, 12 Aug 2012 15:51:30 +0200
From: Samuele Giovanni Tonon <samu@...uxasylum.net>
To: john-dev@...ts.openwall.com
Subject: Re: Result of hard core password generation on 7970
On 08/12/2012 01:33 PM, myrice wrote:
> On Sun, Aug 12, 2012 at 5:28 PM, myrice <qqlddg@...il.com> wrote:
>> On Wed, Aug 8, 2012 at 5:31 AM, Solar Designer <solar@...nwall.com> wrote:
>>> Thanks. Attached is a patch with some optimizations and comments about
>>> further optimizations to make (perhaps after you're done with bitmaps).
>>>
>>> Your direct comparisons, as implemented, turned out to be slower than
>>> local memory bitmap lookups, so I #if 0'ed them out here. If we choose
>>> to implement them, then maybe try it for the case of exactly 1 loaded
>>> hash only, and avoid the array and loop.
>>>
>>> 1
>>> guesses: 0 time: 0:00:01:34 0.00% c/s: 2083M
>>>
>>> 1000
>>> guesses: 0 time: 0:00:01:28 0.00% c/s: 1941G
>>>
>>> These are a bit faster now.
>>>
>>> 1M
>>> guesses: 0 time: 0:00:01:26 0.00% c/s: 851953G
>>>
>>> No speedup for 1M - in fact, a slowdown on this specific test as
>>> compared to your run, but that's kind of random. Indeed, this test is
>>> limited by global memory latency.
>>>
>>> What has happened to the idea of using 4 x 128 MiB bitmaps (like
>>> Multiforcer does) before the hash table lookup (no need to implement
>>> binary search to try this out when we already have the hash table)?
>>> I thought this was on your priorities for this week.
>>>
>>> Thanks,
>>>
>>> Alexander
>>
>> Thanks!
>>
>> I applied your patch and implementing 4 bitmaps. Why this patch didn't
>> work with password generation on CPU and GTX570 on bull? For example,
>> if we have a dictionary file contains a line "passwo" and a hash file
>> with "password" hash. It guessed 0 on CPU and GTX570, but on 7970 it
>> works. If the dictionary file contains "password" directly, then the
>> it can guessed this password.
>
> Already fixed. It is my fault. If the key to crack is less than a
> local work size, the bitmaps is not load correct to local memory. 7970
> may have some optimization on this.
hello myrice,
do you have committed this on github ?
Cheers
Samuele
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.
