From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] polarssl: remove on security grounds
Date: Sat, 29 Oct 2016 15:50:30 +0200 [thread overview]
Message-ID: <20161029155030.36f92ec5@free-electrons.com> (raw)
In-Reply-To: <1477661811-32653-1-git-send-email-gustavo@zacarias.com.ar>
Hello,
On Fri, 28 Oct 2016 10:36:51 -0300, Gustavo Zacarias wrote:
> The 1.2.x branch is no longer maintained and the latest release from the
> maintained branches (2.3, 2.1, 1.3) were security releases, so more
> likely than not 1.2 is affected.
> In consequence switch shairport-sync to the openssl backend.
The question that immediately comes to mind is: if 1.2 is no longer
security-maintained, why don't we package the newer versions such as
2.3 ?
I guess it's because polarssl 2.3 doesn't exist, and it's called
mbedtls instead. But it would be good to get your confirmation, and
have this written clearly in the commit log, and Config.in.legacy help
text.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-29 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 13:36 [Buildroot] [PATCH] polarssl: remove on security grounds Gustavo Zacarias
2016-10-29 13:50 ` Thomas Petazzoni [this message]
2016-11-01 23:27 ` Gustavo Zacarias
2016-11-02 9:45 ` 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=20161029155030.36f92ec5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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