From: Paul Beskeen <email@example.com>
To: Sergei Gavrikov <firstname.lastname@example.org>
Subject: Fwd: [ECOS] Re: PolarSSL for eCos
Date: Thu, 02 May 2013 12:56:00 -0000 [thread overview]
Message-ID: <5182626F.email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2179 bytes --]
Sergei and other maintainers,
IANAL, but I don't think that the PolarSSL FOSS exception is that useful
in the eCos context - eCos itself might be OK is my read - but certainly
not any developer's proprietary embedded application that it is linked
with. I think you should carefully consider the licensing aspects here
before making this an official eCos project.
-------- Original Message --------
Subject: [ECOS] Re: PolarSSL for eCos
Date: Thu, 2 May 2013 14:14:31 +0300 (FET)
From: Sergei Gavrikov <firstname.lastname@example.org>
To: Max SeidenstÃ¼cker <email@example.com>
CC: eCos Discuss <firstname.lastname@example.org>
[Added eCos Discuss to CC]
On Thu, 2 May 2013, Max SeidenstÃÂ¼cker wrote:
> Hi Sergei,
> I am writing you because I saw posts that you successfully ported
> PolarSSL to eCos already.
> For a research project we are currently using eCos and need a TLS1.2
> secured connection. So therefore we need to either update OpenSSL form
> 0.9.6b to 1.0.1, which seems pretty difficult or find an alternative
> SSL library.
> PolarSSL looks really promising, as it also has less ressource usage
> than OpenSSL.
> I am very curious on how far you have come with the porting.
That was a weekend hack only. As far I call correctly the porting
process was straightforward, that GPL PolarSSL version had a few I/O
stubs to overwrite and I have got HTTPS connection on eCos synthetic
target. I had no further work with PolarSSL (and SSL for eCos) but,
IMHO, the project was very promising SSL project ... and IT IS as
thanking your e-mail I knew that PolarSSL team became to provide FOSS
IANAL, but it looks like that we would use GPL PolarSSL 2.0 with that
FOSS exception in eCos. If this so, you would register new eCos project
open eCos Bugzilla entry (http://bugs.ecos.sourceware.org) for the port
and I hope you will find more hands for porting process then. But before
to start I would get confirmation that PolarSSL FOSS License exception
does cover the eCos License exception.
[-- Attachment #2: Attached Message Part --]
[-- Type: text/plain, Size: 149 bytes --]
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next parent reply other threads:[~2013-05-02 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1305021306380.2668@sg-laptop>
2013-05-02 12:56 ` Paul Beskeen [this message]
2013-05-02 14:47 ` Sergei Gavrikov
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).