From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libcurl: enable mbedtls support
Date: Mon, 1 Feb 2016 14:56:13 -0300 [thread overview]
Message-ID: <56AF9C3D.6020805@zacarias.com.ar> (raw)
In-Reply-To: <56AF9B59.4090508@lucaceresoli.net>
On 01/02/16 14:52, Luca Ceresoli wrote:
> 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?
Hi Luca.
Yes, the polarssl comment becomes redundant, since we can't support our
current 1.2.x and we can't (easily) upgrade to 1.3.x, which i think
would be pointless.
Newer openvpn can support 1.3.x but not newer, i know git master which
is very much in a -dev state can do 2.x but i wouldn't pick that up lightly.
Regarding shairport-sync i don't know if it can work with newer
versions, maybe it can do mbedtls directly now that it's been bumped.
Regards.
next prev parent reply other threads:[~2016-02-01 17:56 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
2016-02-01 17:56 ` Gustavo Zacarias [this message]
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=56AF9C3D.6020805@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.