Re: [microblaze-uclinux] Boa + SSL hanging after certificate download

[Jonathan Jung <jwjung@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Ivan,

I may have run across a paper from your project previously... I do  
remember the something about downloading the cores from the network.   
Very interesting indeed!  I'm an undergrad working on this for my  
senior project.

I'm actually 'cheating' a little by using Handel-C for this project  
to create the hardware blocks.  I'll find out how many co-processors  
cores into my FPGA to support different ciphers (starting with AES),  
but I didn't plan to implement a self reconfiguring system (though I  
could work on that, time allowing).

At the time you completed your project, were you using John William's  
FSL driver, or your own?  What was the clock speed of your AES co- 
processor?  How does the FPGA reconfigure itself on the fly (does the  
microblaze continue to run, or does it halt)?

Jonathan
- -------------------------------------
Jonathan Jung
jwjung@xxxxxxxxxxxxx
jonathan.jung@xxxxxxxx

My public key is available on http://www.keyserver.net/en/

On Oct 25, 2005, at 2:14 AM, Ivan wrote:

> El lun, 24-10-2005 a las 23:15 -0700, Jonathan Jung escribió:
>
> > Good news (sort of),
> >
> > I was able to run openssl encryption methods using the openssl app
> > (RC4-40 worked at least ;).
> >
> > Bad news: SSH didn't compile on first run, so I'll have to see why
> > that's freaking out on me.  (don't have the output at the moment).
>
> Hi Jonathan,
>
> about your question to execute 'openssl speed' command on my
> environment, it is not possible because now I am in pre-doctoral  
> stay in
> Switzerland :(
>
> About your problem SSH, I had some problems too, but nothing  
> important.
>
>
> > Still haven't found out why Boa + SSL is hanging, but openssl might
> > be a good substitute for me.
> >
> > BTW, the purpose of getting an encryption/decryption algorithm
> > working is to move the fun parts in to hardware, and connect that
> > hardware via FSL links (and use John's driver)!
>
> My last work was the same that you proposed. I implemented a hardware
> accelerated version of SSH using MicroBlaze-uClinux. The connection
> between MicroBlaze and the cipher cores was made using the FSL
> interface. I tested only the AES-128 and 3DES, but I have implemented
> the IDEA, Blowfish, DES, RC4, MD5 and SHA-128/256 algorithms. In this
> work I measured the performance obtained using the pure-software  
> version
> and the hardware-based version using the scp application. Also, the
> different cipher cores are partial reconfigured at run-time, that is,
> the MicroBlaze downloads from Internet the negotiated cipher core
> (partial bitstream), configures the FPGA (self-reconfiguration) and  
> uses
> it. If the next time the algorithm changes, then MicroBlaze can
> reconfigure the core again with the new cipher :P
> If you are interested, we can talk about it out of the mailing-list
> (because I think that it is an off-topic). I can give some suggestions
> in order to improve my results :)
>
> Regards,
>
> Ivan
>
>
>
> ______________________________________________
> Renovamos el Correo Yahoo!
> Nuevos servicios, más seguridad
> http://correo.yahoo.es
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@xxxxxxxxxxxxxx
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze- 
> uclinux
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/ 
> microblaze-uclinux/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFDXhcq4kOt3FHegqgRAincAJ0a6HxcJD5VPpjWcbmWm3y1A7g9HwCfUaKz
IwT8f0g+Yws/UrQT/8zzVpo=
=jIsD
-----END PGP SIGNATURE-----

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/