GSoC : Bcrypt Implementation on FPGA(status)

[Sandeep Manchella]

Hello,

I would like to report on the status of the qualification task. The code is
attached.

I finished the code and I am still checking the functionality(I got *some
warnings* due to latch development which result in timing delay and wrong
output also sometimes, so trying to fix those) .I based* my
implementation*on the blowfish vhdl code you mentioned in the mailing
list. I obviously
used the same method for init state, P array and S boxes. The control logic
takes care of the expand-key function and encryption in ECB mode as
different states based on simple muxes.

As of now I am trying to make the code free of warnings so that it can be
properly synthesized without any timing delays. If I can complete this in
the next few hours I will post it on www.openwall.com/john/FPGA or mail you
with the screenshots.

Thanking You,
Sandeep.M

P.S : It took me time to understand the blowfish implementation as I newly
learnt vhdl (around 25 days back) and I did my best :) .

[Solar Designer]

Sandeep,

Post by Sandeep Manchella
I would like to report on the status of the qualification task. The code is
attached.

Thanks!

Post by Sandeep Manchella
As of now I am trying to make the code free of warnings so that it can be
properly synthesized without any timing delays. If I can complete this in
the next few hours I will post it on www.openwall.com/john/FPGA or mail you
with the screenshots.

I think it's fine for you to upload draft revisions to the wiki, noting
their status (e.g., known bugs) - like you did in your list posting.
Please do. The wiki page is http://openwall.info/wiki/john/FPGA - you
may create a separate section for your stuff, like it's done on
http://openwall.info/wiki/john/GUI - or you may create a sub-page.

Also, please license your code such that others can reuse it (not
necessarily us and not necessarily for this project, but in general):

http://openwall.info/wiki/john/licensing

Thanks again,

Alexander

[Sandeep Manchella]

Hi,
My end-semester exams are going on now, so I don't think its possible
for me to that now. As I spent a lot of time on it, I would like to get to
rid of the bugs and upload the proper working version after my exams are
done(anyway 12 weeks holidays) if its okay with you ?
Thanking You,
Sandeep.M

Post by Solar Designer
Sandeep,

Post by Sandeep Manchella
I would like to report on the status of the qualification task. The code

is

Post by Sandeep Manchella
attached.

Thanks!

Post by Sandeep Manchella
As of now I am trying to make the code free of warnings so that it can be
properly synthesized without any timing delays. If I can complete this in
the next few hours I will post it on www.openwall.com/john/FPGA or mail

you

Post by Sandeep Manchella
with the screenshots.

I think it's fine for you to upload draft revisions to the wiki, noting
their status (e.g., known bugs) - like you did in your list posting.
Please do. The wiki page is http://openwall.info/wiki/john/FPGA - you
may create a separate section for your stuff, like it's done on
http://openwall.info/wiki/john/GUI - or you may create a sub-page.
Also, please license your code such that others can reuse it (not
http://openwall.info/wiki/john/licensing
Thanks again,
Alexander

[Solar Designer]

Post by Sandeep Manchella
My end-semester exams are going on now, so I don't think its possible
for me to that now. As I spent a lot of time on it, I would like to get to
rid of the bugs and upload the proper working version after my exams are
done(anyway 12 weeks holidays) if its okay with you ?

In Open Source, the right thing to do is to share your draft revisions
of the code as well - like you did by attaching one to your posting,
however you could do it better by adding a licensing statement and
uploading to the wiki. I don't think this will take you much time.
We're unlikely to make any use of this code, but someone else might find
it with a search engine and use it (directly or for inspiration). It is
just about preserving your time investment for the benefit of the Open
Source community at large. It is a good idea for you to make a habit to
share your code in a reusable fashion.

As to getting rid of the bugs and uploading a new revision, of course
feel free to do that as well. Just not as a replacement to uploading
the current revision.

Of course, the above are just my suggestions. You're the one to decide
on what to do with your code.

Thanks,

Alexander