[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 15 Sep 2013 20:33:45 +0200
From: Katja Malvoni <kmalvoni@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: ZedBoard / Parallella: bcrypt
Hi Alexander,
2. However, when I tried to actually crack passwords, nothing got
> cracked, even though john proceeds through the wordlist at this same
> speed. (I ran it as root, after a "sudo bash", so that the status
> display on keypress worked for me.) Obviously, you need to get this to
> work.
>
At one moment I hard coded cost to be 5 and I forgot about it so it works
only for cost 5 hashes. I'm testing it with cost 12 and I'm getting cracks
so it works now.
> 3. bcrypt.bit.bin doesn't include(?) Epiphany support, right? At least
> my attempt to use format bcrypt-parallella failed (the john process was
> stuck at 100% host CPU, presumably waiting for Epiphany), until I loaded
> the Parallella project provided bitstream back. Can the Epiphany
> support be re-added without too much cost in FPGA resource utilization?
> I guess the 1200+ c/s that we're getting from Epiphany may exceed
> whatever we'll get from that portion of FPGA resources (or maybe not -
> we'll see for real later).
>
It does include Epiphany support and I'm not sure why it doesn't work. I'm
sure that in one point I tested bcrypt-parallella and it passed self test.
But I really can't remember was it with current bitstream or with one of
previous versions but it sure was bitstream I generated. Now it doesn't
work for me either.
I generated few bitstreams and in some cases Epiphany can be reached and in
some cases it can't. I don't undestand why because I'm only changing my
bcrypt IP and it doesn't use any of Epiphany resources. At the moment I do
have bitstream file with Epiphany support (format bcrypt-parallella passes
self test).
And just when I finished writing this and tried it one more time it failed
self test. I tried to load same bitstream again and now zed system is
locked up. I have no idea what just happened.
> 4. In BF_std.c, can you separate your added code into a new source file
> and invoke it via function calls? At the same time, make it clear what
> license applies to your added code.
>
Done.
> 5. Can you easily split bcrypt.v into several source files, separating
> your hand-written code from Xilinx's code and from auto-generated code?
>
I'll try, I think it should be possible.
> 6. Once you get the current code working for real (cracking passwords),
> please proceed with implementation and usage of multiple bcrypt cores,
> and with optimizations.
>
At the moment it's on around 390000 clock cycles with dual port ram
(simulation works, not tested on Zedboard).
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.
