[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130627150451.GA23048@openwall.com>
Date: Thu, 27 Jun 2013 19:04:51 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: Katja's weekly report #2
On Thu, Jun 27, 2013 at 04:49:54PM +0200, Katja Malvoni wrote:
> On Thu, Jun 27, 2013 at 4:44 PM, Solar Designer <solar@...nwall.com> wrote:
> > On Mon, Jun 24, 2013 at 04:52:17PM +0200, Katja Malvoni wrote:
> > > 2. Project timeline defined
> >
> > Where is it?
>
> Well, If I got it right, we agreed that I first finish implementing bcrypt
> on Epiphany and than continue with implementation on FPGA starting with
> Zynq and than with some other bigger FPGA.
> Bcrypt on Epiphany will take about one week of work (maximally 10 days) and
> after that I start with FPGAs.
Sounds fine.
> > > 2. Implementing bcrypt on all Epiphany cores
[...]
> I did that already. It's running on all cores now.
That's great news. :-) Going forward, please post in here about your
progress - not only the mandatory weekly reports, but also whenever you
do make some progress. (Yet the weekly reports should list everything
since the previous weekly report in "accomplishments".)
> At the moment, all cores
> use the same key and setting, I'm currently working on writing key and
> setting from host into each core so that each core can run with different
> key and setting.
For use in JtR, we only need each core to process its own key, but the
setting will be the same for all cores.
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.
