[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <369e2e353759a1310f677c0e83aa262e@smtp.hushmail.com>
Date: Sun, 19 Aug 2012 20:02:45 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: int crypt_all(count, salt)
On 2012-08-19 17:11, Solar Designer wrote:
> On Sun, Aug 19, 2012 at 12:06:59PM +0200, magnum wrote:
>> On 2012-07-21 15:27, Solar Designer wrote:
>>> john-1.7.9.6-crypt_all-pcount-1.diff - applies on top of clean 1.7.9.6
>>> as found in CVS.
>>
>> This patch includes everything new, right?
>
> Yes, it has everything that I prepared for myrice's experiments so far.
>
>> Should I merge this into
>> bleeding? I thought they were going into CVS soon so I waited (because
>> it will be better for future git history) but it's still not in.
>
> I think I'll get something like this into CVS eventually - I'm not sure
> how soon that will be. Do you want to have this in bleeding, even
> though you'll need to replace it with whatever gets committed to CVS
> later?
Maybe not. I'm mostly curious about done() and the faster self-test
right now.
> FYI, I expect that myrice will take a short break, so having
> this in bleeding won't be helping the project yet. Now, in case we want
> to merge the PG-test stuff into bleeding, we'll definitely need these
> changes in bleeding first. But do we want this stuff in there, with the
> hard-coded appended chars?
Not unless it helps someone. I think I'll just have a look at it in a
scratch branch.
magnum
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.
