This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Re: On Porting OpenSSL v1.0.0c


On Thu, 9 Dec 2010, Michael Bergandi wrote:

> On Tue, Dec 7, 2010 at 11:32 AM, Michael Bergandi wrote:
> >
> > Hello all,
> >
> > I would like to know if there is someone interested or already
> > working on a port of the latest OpenSSL library to eCos. If you are
> > or know someone who is, I would love to know about it so that we are
> > not duplicating efforts.
> >
> > In doing some online research regarding OpenSSL on eCos, I came
> > across the old port of OpenSLL by Andrew Lunn that claims to be
> > updated to the v0.9.6b code base. However, that port is quite dated
> > (going on 9 years old) and the current code base is much much
> > different now.
> >
> > I also came across a note from Andres in the archives in response to
> > someone else's inquiry about using the SSL portion of the library:
> >
> > > Please not that i only used some of the encryption algorithms and
> > > diffie Hellman from it. I've not used SSL. So expect it to be
> > > broken and require some work. You may be luck and its works
> > > perfectly.
> > >
> > > If you do plan on update to a newer version of OpenSSL, please let
> > > me know, i have a few suggestions....
> > >
> > > Â ÂAndrew
> >
> > Well, Andrew, if you are listening, I'm all ears...
> >
> > The project I am working on will be using SSL to provide a secure
> > web interface for device configuration. In addition, we want to
> > leverage the encryption module on our processor (mx27) to get some
> > hardware acceleration for our other encryption needs. The ENGINE
> > interface, in particular, is the primary reason for our desire to go
> > ahead and port the latest OpenSSL to eCos.
> >
> > So, again, if anyone wants to be a part of this effort or can be
> > there to offer guidance along the way, please let me know and we can
> > collaborate.
> >
> > Thanks for you interest and comments,
> >

Hi,

My 2 cents:

I would look at PolarSSL
1) http://polarssl.org/features
2) http://polarssl.org/licensing

IMO, point #2 is valuable thing to port PolarSSL to eCos.

Yet another candidate with dual licensing also would be... yaSSL
http://www.yassl.com/yaSSL/License.html

However, IANAL.

But, both these SSL libraries were designed with a word "embedded" in a
mind.

Well, OpenSSL has much muscles, but, What's about thin SSL for embedded
World (=eCos)?

Thanks,
Sergei

> > --
> > Michael Bergandi
> 
> Perhaps this inquiry is better suited for the ecos-devel mailing list?
> 
> --
> Michael Bergandi
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]