Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libcurl: enable mbedtls support
Date: Mon, 1 Feb 2016 18:52:25 +0100	[thread overview]
Message-ID: <56AF9B59.4090508@lucaceresoli.net> (raw)
In-Reply-To: <56AF88F9.2000904@zacarias.com.ar>

Hi Gustavo,

Gustavo Zacarias wrote:
> On 01/02/16 13:27, Luca Ceresoli wrote:
>
>> This is unrelated to your change, it should be a separate patch. But
>> anyway I don't understand why it should be removed: we still package
>> polarssl 1.2.18, so the comment should still apply. Am I missing
>> something?
>>
>> With that fixed (or explained):
>>   Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net>
>>
>> And:
>> [Built with/without mbedtls, ran on qemu, checked that 'curl -V' shows
>> the SSL only with mbedtls]
>> Tested-by: Luca Ceresoli <luca@lucaceresoli.net>
>
> Hi.
> As you know polarssl was renamed to mbedtls when bought by ARM, this was
> circa the 1.3.x release.
> Older 1.3.x releases install the library as polarssl alone, newer ones
> install dual as polarssl with symlinks to mbedtls (might be the other
> way around, i don't recall at the moment - it doesn't matter anyway), so
> first the distinction between polarssl and mbedtls is terribly blurred
> for the 1.3.x series.
> Incidentally this is what makes polarssl 1.2.x being able to live
> side-by-side with mbedtls (2.x, which doesn't keep legacy handling) (i
> believe this is more product of branding/accident than careful thinking).
> So now in some cases polarssl means 1.2.x, in other cases it means
> mbedtls 1.3.x, or the new version because nobody cared to rename
> everything.
> Basically any explanation given out of context is useless without
> historical context.
> Making 1.3.x live side-by-side with mbedtls (let's call it that way for
> 2+) is probably possible by ditching the new naming and just keeping
> compat, i had a look but i think it was a dead end anyway, this requires
> patching the build of mbedtls/polarssl 1.3.x somewhat and that wouldn't
> be accepted upstream.

Thank you for the explanation. Indeed, it got me totally puzzled! I am
no mbedtls/polarssl expert, I never used them...

If I understand correctly:
  - without this patch, the comment states that you'd need to upgrade
    polarssl to 1.3.x to have it supported in libcurl
  - with the patch libcurl uses mbedtls, which makes polarssl
    uninteresting.

Is it correct?

-- 
Luca

  reply	other threads:[~2016-02-01 17:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 18:53 [Buildroot] [PATCH] libcurl: enable mbedtls support Gustavo Zacarias
2016-02-01 16:27 ` Luca Ceresoli
2016-02-01 16:34   ` Gustavo Zacarias
2016-02-01 17:52     ` Luca Ceresoli [this message]
2016-02-01 17:56       ` Gustavo Zacarias
2016-02-01 18:02         ` Luca Ceresoli
2016-02-01 18:03           ` Gustavo Zacarias
2016-02-01 18:07             ` Luca Ceresoli
2016-02-01 18:08               ` Gustavo Zacarias
2016-03-08 20:26 ` Thomas Petazzoni

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56AF9B59.4090508@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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