Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e877d7a8fa62a3fcc5580ed239631bc@smtp.hushmail.com>
Date: Tue, 7 May 2013 09:10:39 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Enhancements to pbkdf2-sha256

On 7 May, 2013, at 8:53 , magnum <john.magnum@...hmail.com> wrote:
> WAT!?, so you went from 4K to 24K without even starting to use SSE2? Wow. If you're not done with SSE2 SHA-512 in time for 1.8-Jumbo-1 we should simply wait until it's ready. We can release 1.7.9-Jumbo-8 in the meantime :-)

Just for reference, here's Hashcat speeds:

From http://hashcat.net/forum/thread-2247.html:
> Here are the speeds, captured on a stock clocked AMD FX™-8120 Eight-Core Processor using 8 threads:
> 	• {smd5} 80.60 KH/s
> 	• {ssha1} 822.22 KH/s
> 	• {ssha256} 394.14 KH/s
> 	• {ssha512} 175.61 KH/s

We are definitely faster with smd5 (now supported in md5crypt format). With OMP we get ~200K and with -fork we might do 50% more (or will it decrease the clock too much for that? It's a pity you cant --test with --fork).

We should split aix-ssha into three different formats (in one same source file). We currently benchmark a mix of test vectors :-/

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.