[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120430233336.GB9024@openwall.com>
Date: Tue, 1 May 2012 03:33:36 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: JtR compilation warnings on OS X 10.7.3 with Xcode 4.3.2
On Mon, Apr 30, 2012 at 07:41:47PM +0530, Dhiru Kholia wrote:
> On Mon, Apr 30, 2012 at 1:51 AM, Solar Designer <solar@...nwall.com> wrote:
> > What was the input size - was the compression function invoked just once
> > per cycle or more than once?
>
> Once per cycle.
>
> for(i = 0; i < 10000000; i++) {
> SHA1_Init(&ctx);
> SHA1_Update(&ctx, message, n);
> SHA1_Final((unsigned char *)sha1hash, &ctx);
> }
Actually, my question was about strlen(message). For a long message, a
single call to SHA1_Update() results in multiple invocations of the
compression function. Well, I guess the message was short - which is
what we usually care about in JtR.
> > Can you repeat this test for SHA-512?
>
> $ ../run/john -format=raw-sha512 -t # before
> Benchmarking: Raw SHA-512 [64/64]... DONE
> Raw: 1046K c/s real, 1056K c/s virtual
>
> $ ../run/john -format=raw-sha512 -t # after
> Benchmarking: Raw SHA-512 [64/64]... DONE
> Raw: 1322K c/s real, 1349K c/s virtual
Wow. This is more impressive. What CPU are you on? Can you try to
make this change for XSHA512 and benchmark it before/after, including
with an OpenMP-enabled build? (We don't currently have OpenMP support
for raw SHA-512. By the way, this is fairly easy to correct.)
OK, let's switch to CommonCrypto for now.
Thanks,
Alexander
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.
