From: akuster808 <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org,
joshua.g.lock@intel.com, akuster@mvista.com
Subject: Re: [fido][PATCH 0/7] fido Security fixes pull request
Date: Sun, 28 Feb 2016 08:39:21 -0800 [thread overview]
Message-ID: <56D322B9.2010906@gmail.com> (raw)
In-Reply-To: <cover.1456242658.git.akuster@mvista.com>
ping
On 02/23/2016 07:58 AM, Armin Kuster wrote:
> From: Armin Kuster <akuster@mvista.com>
>
> Please consider these for the next fido
>
> This is to meet our obligation for Yocto compatibility
>
> The following changes since commit 06d9c894636352a6c93711c7284d02b0c794a527:
>
> libbsd: Security fix CVE-2016-2090 (2016-02-18 11:03:10 +0000)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib akuster/fido_cve_fixes
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akuster/fido_cve_fixes
>
> Armin Kuster (7):
> qemu: Security fix CVE-2016-2198
> foomatic-filters: Security fix CVE-2015-8560
> foomatic-filters: Security fixes CVE-2015-8327
> tiff: Security fix CVE-2015-8781
> tiff: Security fix CVE-2015-8784
> librsvg: Security fix CVE-2015-7558
> gdk-pixbuf: Security fix CVE-2015-7674
>
> .../recipes-devtools/qemu/qemu/CVE-2016-2198.patch | 45 ++++
> meta/recipes-devtools/qemu/qemu_2.2.0.bb | 1 +
> .../foomatic-filters-4.0.17/CVE-2015-8327.patch | 23 +++
> .../foomatic-filters-4.0.17/CVE-2015-8560.patch | 23 +++
> .../foomatic/foomatic-filters_4.0.17.bb | 4 +
> .../gdk-pixbuf/gdk-pixbuf/CVE-2015-7674.patch | 39 ++++
> meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.30.8.bb | 1 +
> .../librsvg/librsvg/CVE-2015-7558_1.patch | 139 +++++++++++++
> .../librsvg/librsvg/CVE-2015-7558_2.patch | 230 +++++++++++++++++++++
> .../librsvg/librsvg/CVE-2015-7558_3.patch | 223 ++++++++++++++++++++
> meta/recipes-gnome/librsvg/librsvg_2.40.6.bb | 6 +-
> .../libtiff/files/CVE-2015-8781.patch | 196 ++++++++++++++++++
> .../libtiff/files/CVE-2015-8784.patch | 73 +++++++
> meta/recipes-multimedia/libtiff/tiff_4.0.3.bb | 5 +-
> 14 files changed, 1006 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-2198.patch
> create mode 100644 meta/recipes-extended/foomatic/foomatic-filters-4.0.17/CVE-2015-8327.patch
> create mode 100644 meta/recipes-extended/foomatic/foomatic-filters-4.0.17/CVE-2015-8560.patch
> create mode 100644 meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/CVE-2015-7674.patch
> create mode 100644 meta/recipes-gnome/librsvg/librsvg/CVE-2015-7558_1.patch
> create mode 100644 meta/recipes-gnome/librsvg/librsvg/CVE-2015-7558_2.patch
> create mode 100644 meta/recipes-gnome/librsvg/librsvg/CVE-2015-7558_3.patch
> create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2015-8781.patch
> create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2015-8784.patch
>
next prev parent reply other threads:[~2016-02-28 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 15:58 [fido][PATCH 0/7] fido Security fixes pull request Armin Kuster
2016-02-28 16:39 ` akuster808 [this message]
2016-02-29 15:16 ` Joshua G Lock
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=56D322B9.2010906@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=joshua.g.lock@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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