Date: Tue, 20 Aug 2013 20:22:01 +0200 From: Katja Malvoni <kmalvoni@...il.com> To: john-dev@...ts.openwall.com Subject: Re: Parallella: bcrypt On Tue, Aug 20, 2013 at 7:59 PM, Solar Designer <solar@...nwall.com> wrote: > On Tue, Aug 20, 2013 at 05:24:17PM +0200, Katja Malvoni wrote: > > From postings I got > > impression that only thing which can be done is to check whether data is > > transferred correctly before writing start flag. So I changed code to do > > that - removed start arrays from inputs structure and put only one start > > array in shared_buffer structure. And did check of transferred data. That > > didn't help. Am I missing something here? > > How did you implement the "check of transferred data"? > I use e_write to write inputs structure and immediately after it I read from the same location in check_input variable. This read after write should be ok - http://www.openwall.com/lists/john-dev/2013/07/26/10. And than I check that input and check_input have the same values. That's a weird solution, and one that does not make me comfortable about > its reliability, given how very fragile you say it is. > I agree and I don't completely understand why it seems to be working. > > If I read keys from external memory always than > > it seems to be working. But if keys are read only when changed than it > > cracks around 25000 passwords. > > This is puzzling. It suggests that some further action is attempted too > soon when the keys are not re-read... but the only other thing you're > reading is the salt, and you read it before the keys, right? Puzzling. > Yes, I only read salt. Keys in local memory shouldn't change but either they change or ones in shared buffer are incorrect. Katja Content of type "text/html" skipped
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.