This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: On Porting OpenSSL v1.0.0c
- From: John Dallaway <john at dallaway dot org dot uk>
- To: Sergei Gavrikov <sergei dot gavrikov at gmail dot com>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 14 Dec 2010 18:59:53 +0000
- Subject: [ECOS] Re: On Porting OpenSSL v1.0.0c
- References: <AANLkTi=3hSnicTZ77Ci3Nfw9BEMYYv3Cg4Ub_kpA12QD@mail.gmail.com> <C4E8D0478C3D194FA02B65678CBB6C6087A78E6E66@DEFTHW99EC5MSX.ww902.siemens.net> <4D073A3D.9040706@dallaway.org.uk> <alpine.DEB.2.00.1012141657100.16021@sg-laptop>
Hi Sergei
Sergei Gavrikov wrote:
> If we can have only the 3rd party crypto packages, that's good to have
> different alternatives. And 2-3 alternatives is not too much :-)
>
> Well, as I said 'A', I will work on CYGPKG_POLARSSL. Certainly, that will
> be movements only in porting and testing. I am not expert in the field of
> cryptography.
Great! If the PolarSSL footprint is significantly smaller than OpenSSL
with an equivalent feature set configured, then your port could prove to
be very useful for projects where the unmodified GPL is not an issue, or
for projects where a commercial PolarSSL license makes sense.
John Dallaway
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss