From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tiff: bump version to 4.0.7 (security)
Date: Mon, 21 Nov 2016 21:17:11 +0100 [thread overview]
Message-ID: <20161121211711.1eaa3666@free-electrons.com> (raw)
In-Reply-To: <20161121101350.31299-1-Vincent.Riera@imgtec.com>
Hello,
On Mon, 21 Nov 2016 10:13:50 +0000, Vicente Olivert Riera wrote:
> Fixed CVEs:
> - CVE-2016-3622
> - CVE-2016-3623
> - CVE-2016-5321
> - CVE-2016-5323
> - CVE-2016-5652
> - CVE-2016-5875
> - CVE-2014-8127
> - CVE-2015-8665
> - CVE-2015-8683
> - CVE-2016-9273
> - CVE-2016-9448
>
> Release notes: http://www.simplesystems.org/libtiff/v4.0.7.html
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> package/tiff/tiff.hash | 2 +-
> package/tiff/tiff.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-21 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 10:13 [Buildroot] [PATCH] tiff: bump version to 4.0.7 (security) Vicente Olivert Riera
2016-11-21 20:17 ` Thomas Petazzoni [this message]
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=20161121211711.1eaa3666@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