[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <003601cd5642$a4782560$ed687020$@net>
Date: Fri, 29 Jun 2012 17:00:48 -0500
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: For some dynamic formats on linux-x86-mmx build cracking depends on password candidate sequence
Fixing that with a work around like that, should not be done. If there is some overwrite happening, or key cleaning needing done, then we need to find it.
For a md5(md5($p)) format, the buffer 2 is ONLY used to hold 32 byte strings. It should never need to be cleaned up. The 2nd half of the buffer simply needs set, and left alone. Makes no difference at all on builds other than SSE. But on SSE builds, it can make a significant difference.
>And, of course, the workaround code change posted for dynamic_2 earlier
>in this thread works as well. But that costs 2.5 - 3 % performance for
>my 32 bit linux-x86 builds.
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.
