[Buildroot] [PATCH] Update from polarssl to mbed 1.3.11

[Gustavo Zacarias <gustavo@zacarias.com.ar>]

On 17/07/15 04:52, Thomas Petazzoni wrote:

> Arnout, Ed,
>
> On Fri, 17 Jul 2015 00:32:59 +0200, Arnout Vandecappelle wrote:
>
>>> Thanks for your patch. However, following Gustavo's comment, I've
>>> marked your patch as "Changes Requested" in our patch tracking system.
>>> Can you resubmit a new version that takes into account Gustavo's
>>> comments?
>>
>>   Since it anyway is not compatible and upstream changed name, perhaps it's
>> better just to create a new package called mbedtls? When we remove polarssl we
>> can make a legacy entry to point to mbedtls.
>
> Why would we remove polarssl? Is the project dead? Or is mbedtls its
> replacement?
>
> Other than that, yes: if mbedtls is like a new library that is
> incompatible with polarssl, then a separate package is the best option.

mbedtls is polarssl, it just got renamed when they got bought by ARM.
Adding to confusion this was done with the 1.3+ branches but not with 
1.2 (which is in security maintenance).
It was to reflect that polarssl (now mbedtls) is the crypto library for 
the mbed operating system, even though it still works with linux (likely 
they enabled this with 1.3+ but never backported to 1.2- hence keeping 
the old name).
Last time i've checked the 1.2 and 1.3 series couldn't coexist sanely on 
the same system, and since programs checks for polarssl rather than 
mbedtls for now it's probably still the case.
rtmpdump can use any of the three optionally (gnutls, openssl, 
polarssl), dunno if it can handle 1.3+
curl needs 1.3+ (we never enabled polarssl support).
Newer hiawatha needs 1.3+ (or can use bundled).
shairport-sync can use either polarssl or openssl (mandatory one of 
them), dunno if it can handle 1.3+
openvpn can use openssl or polarssl (not 1.3+).
So it basically narrows down the choices, though it doesn't necessarily 
take down other packages.
Question is, keep 1.2 and some small targets small or go 1.3+ ?
Also there's mbedtls 2.0.0 now, which, again, breaks API. And this has a 
better chance of living side by side with polarssl 1.2 since they've 
renamed everything it seems.
Regards.