[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 06 Feb 2006 03:26:53 +0100
From: Michal Luczaj <regenrecht@...pl>
To: john-users@...ts.openwall.com
Subject: Re: DIGEST-MD5, dominosec optimization (was: IPB2, DIGEST-MD5,
salted domino)
Solar Designer wrote:
> Thanks. I've placed these two in contrib/ and linked them from the
> website, although I am not sure the DIGEST-MD5 one should be "announced"
> like that since it can't be used without the source file being further
> modified for the specific sniffed session.
I know, I know. And I really don't mind removing link from website :)
Your're right; JtR's main site shouldn't be hosting every, err,
experiment. If someone need it, he'll find it... or write by himself.
> Well, maybe you will provide a generic implementation later. ;-)
Well, maybe I will ;) Really, I though that this *something* is so
specific, that any generalization would be just a redundant overhead.
> Why did you mention "salted domino" in the Subject, though?
Because I was mentioning about salted domino patch optimization :>
Little inconsistency as I was also referring to single/incremental
discussion.
> I mean, the algorithms and code used in unofficial patches
> for John are not really optimized anyway. You can likely achieve much
> greater speedups by optimizing the source code.
I'd love to! Any hints? :)
> Yes, I might be forced to introduce something like that eventually, but
> not for that reason. "configure" scripts are not expected to guess gcc
> optimization options; they accept CFLAGS from the environment.
I see. So what for this ./configure-like thingie would be used?
Michal
Powered by blists - more mailing lists
Powered by Openwall GNU/*/Linux -
Powered by OpenVZ