From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/iucode-tool: security bump to version 2.2
Date: Sat, 7 Oct 2017 23:12:17 +0200 [thread overview]
Message-ID: <20171007231217.3c4aca8b@windsurf.home> (raw)
In-Reply-To: <20171007110209.26248-1-bernd.kuhls@t-online.de>
Hello,
On Sat, 7 Oct 2017 13:02:08 +0200, Bernd Kuhls wrote:
> Version 2.1.1 fixed CVE-2017-0357:
> https://gitlab.com/iucode-tool/iucode-tool/commit/657ce44ac462bcec35a3e12f9e7f53ca92ae62b7
>
> Dropped IUCODE_TOOL_CONF_ENV after version 2.2 added a configure check
> for libargp:
> https://gitlab.com/iucode-tool/iucode-tool/commit/b14bed6771e7ab48371b272a0c68dd017767142a
>
> Added hash for license file.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/iucode-tool/iucode-tool.hash | 3 ++-
> package/iucode-tool/iucode-tool.mk | 3 +--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Both applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-07 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 11:02 [Buildroot] [PATCH 1/2] package/iucode-tool: security bump to version 2.2 Bernd Kuhls
2017-10-07 11:02 ` [Buildroot] [PATCH 2/2] package/intel-microcode: bump to version 20170707 Bernd Kuhls
2017-10-07 21:12 ` Thomas Petazzoni [this message]
2017-10-14 20:23 ` [Buildroot] [PATCH 1/2] package/iucode-tool: security bump to version 2.2 Peter Korsgaard
2017-10-17 9:06 ` Peter Korsgaard
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=20171007231217.3c4aca8b@windsurf.home \
--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