lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-devel] PolarSSL -> mbed TLS


From: Elias Önal
Subject: Re: [lwip-devel] PolarSSL -> mbed TLS
Date: Wed, 9 Mar 2016 18:42:35 +0800
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0

I have used LibTomCrypt on bare metal targets before and can highly recommend it. Given that it's public domain there wouldn't be any license issues. It's a bit more complex than mbedTLS, yet especially the documentation is much better from my experience.

-Elias

On 09/03/16 03:28, Sg wrote:
Hey Jonathan, you're alive ;-) nice to hear from you!

Thank you for the hint on the licenses. I wouldn't want to include the mbed sources, only provide a way of somehow using them so that the actual work of combining them is done by the user (or a distributor). We wouldn't want to keep a copy of these files updated in our repository...

We do have the old polarssl files because they are harder to get (and given the license break, they don't change), but getting an up-to-date copy mbed TLS should not be too hard.

Ideally our sources should compile with both versions.

Simon


Gesendet mit AquaMail für Android
http://www.aqua-mail.com


Am 8. März 2016 20:12:40 schrieb Sylvain Rochet <address@hidden>:

Hi Jonathan,

On Tue, Mar 08, 2016 at 06:42:19PM +0000, Jonathan Larmour wrote:
On 07/03/16 22:54, Sylvain Rochet wrote:
> On Wed, Feb 24, 2016 at 09:43:26PM +0100, address@hidden wrote:
> > I just wondered: now that PolarSSL has been bought by ARM and the
> > successor, mbed TLS is available under a non-GPL license again
> > (Apache): [snip]
>
> We can probably allow using ASL in lwIP, it reaches my limit at
> understanding slight differences between licenses, from my opinion
> it's as free as BSD.

According to the FSF, it's not compatible with the GPLv2 [1], only
GPLv3. That is why mbed TLS is dual licensed with GPLv2:
https://tls.mbed.org/how-to-get

Some care would be needed in how it is incorporated into lwIP, or
perhaps, incorporating would be the wrong approach and it should just be a case of the user linking against an mbed TLS they've built themselves.

You are right, I didn't thought of that although I already known that
the main difference between ASL and BSD is that files under ASL can't be
relicensed under another license. Since mbed TLS is dual licensed with
GPLv2 that doesn't stop it to be included. If it were not dual licensed
it would have prevented lwIP to be used in a GPLv2 project and it would
then have been blocking for inclusion in lwIP. Correct me if I am wrong :-)

Sylvain



----------
_______________________________________________
lwip-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-devel




_______________________________________________
lwip-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-devel





reply via email to

[Prev in Thread] Current Thread [Next in Thread]