Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110817200607.GA30433@openwall.com>
Date: Thu, 18 Aug 2011 00:06:07 +0400
From: Solar Designer <solar@...nwall.com>
To: crypt-dev@...ts.openwall.com
Subject: Re: Yuri's Status Report - #12 of 15

Yuri, David -

Now that David restored our access to the machine (thanks!), I got
Yuri's modified John the Ripper tree to build.

On Tue, Aug 02, 2011 at 05:22:45AM -0300, Yuri Gonzaga wrote:
> I started to integrate JtR with one core using the patched provided.
> However, I can't get sucess in compiling all together.
> It was possible to generate *.o files from $(PICOBASE)/software/source.
> But, calls to JtR's Makefile are getting a lot of strange errors I couldn't
> overcome until now.
> Maybe, the mixture of JtR's C code with Pico's C++ one is causing this
> problem in compilation.

Yes, this was one of the primary problems.  Not so much the fact that
Pico's *.o's were compiled from C++ files, but primarily the fact that
Pico's header files were also C++'ish.  Anyway, I managed to mix them
such that the thing builds.  Please see john-s-1.diff and john-s-2.diff
in your home directory to find out what changes I made in the john-s
tree relative to your john tree.

Now it fails at runtime when actually trying to communicate to the FPGA:

yuri@...iplex980:~/john-s/src$ ../run/john -te -fo=bf
Benchmarking: OpenBSD Blowfish (x32) [32/64 X2]... Error Writing: -1

Yuri - it's your turn.  I guess you need to actually load the bitstream
into the FPGA somewhere/somehow.  Do you know how to do that on this
machine?  Did you successfully access the FPGA with the sample programs?

Please let us know.

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.