Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANJ2NMMMb1gT0PF5KSunfBPbeW3ZQgXQ9WdBCa8xGMwCm-9Z9g@mail.gmail.com>
Date: Sat, 21 Jul 2012 21:52:03 +0800
From: myrice <qqlddg@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: int crypt_all(count, salt)

On Sat, Jul 21, 2012 at 9:31 PM, Solar Designer <solar@...nwall.com> wrote:
> myrice -
>
> On Wed, Jul 18, 2012 at 02:10:41PM +0400, Solar Designer wrote:
>> BTW, how did you locate the hashes corresponding to the current salt on
>> GPU in your existing (now lost?) implementation of loaded hashes?  Did
>> you possibly implement some hash table lookups by salt value?  Or do you
>> assume that crypt_all() is called for all salts sequentially (in the
>> same order they were seen before)?  (This might be risky.)
>
> I think you never replied to the above.  Please do.
>

In my previous implementation. I suppose the latter case you said. I
am going to implement hash table by salt value or either add salt_id
as you said.

Thanks
myrice

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.