[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130809133859.GA31497@openwall.com>
Date: Fri, 9 Aug 2013 17:38:59 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: Parallella: bcrypt
Katja,
On Mon, Aug 05, 2013 at 07:19:07PM +0200, Katja Malvoni wrote:
> I run self test until it stalled. It happens in while loop on host side.
> One of the cores (first time it was 14, second time 13, third time 15)
> stalls somewhere before do while loop. I checked shared DRAM, 16 is written
> in memory for both start arrays for that specific core so conditions in
> while loops are true but it never reaches BF_crypt() call nor resetting
> start flags. I also added writing different number instead of result after
> every line in main on Epiphany side - core that stalls never reached first
> write that was before do while loop. Only zeroes were in memory for result
> and core_done flag for that core. All the other cores except the one that
> stalls work correct. And it happens only in first cryp_all call. So far it
> never happened in the middle of computation. It seems as that one core
> never starts computation.
This is a separate problem from the other reliability problem you had
reported (sometimes cracking one password less than expected), right?
So we've got two reliability problems in the current code, right?
What do you intend to do about these?
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.
