Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 21 Jan 2013 20:20:56 +0530
From: Dhiru Kholia <>
Subject: Re: Proposed optimizations to pwsafe

On Mon, Jan 21, 2013 at 9:44 AM, Brian Wallace
<> wrote:
> I got some time before I thought I would have any, and dug around the source
> to get an idea of how data flows in JtR.  I've done a preliminary
> implementation of the optimization in my forked repository, with some gains.
> Old:
> ./john --test=15 --format=pwsafe
> Benchmarking: Password Safe SHA-256 [32/64]... (6xOMP) DONE
> Raw:    7027 c/s real, 1213 c/s virtual
> New:
> ./john --test=15 --format=pwsafe
> Benchmarking: Password Safe SHA-256 [32/64 OpenSSL]... (6xOMP) DONE
> Raw:    8268 c/s real, 1395 c/s virtual

Great. The new code sacrifices readability but I guess that's the
price one has to pay for increased performance.

> My fork:

I will test it soon on x86-64 and PPC. If it works fine, can I ask you
to send a pull request on GitHub?

> Looking at the cuda version, the optimizations seems to already be applied
> but I haven't checked the opencl version yet.


Any comments on this one?


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.