Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kai Kang <kai.kang@windriver.com>
To: <randy.macleod@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] Fix CVE issues and add new libav recipe
Date: Thu, 28 May 2015 09:26:13 +0800	[thread overview]
Message-ID: <cover.1432775689.git.kai.kang@windriver.com> (raw)

* Fix CVE issues for severial packages
* Upgrade libav  9.61 --> 9.18
* Add recipe for libav series 11

Build world for x86-64 and qemuarm are fine except some textrel warnings for qemuarm.
Should I open new defects that?

--Kai

The following changes since commit a431e5aa572358ba61cf3c9e501f830263bdcd3d:

  bitbake: data: Make expandKeys deterministic (2015-05-27 17:48:06 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib kangkai/CVEs
  http://git.yoctoproject.org/cgit.cgi//log/?h=kangkai/CVEs

Kai Kang (5):
  gpgme: fix CVE-2014-3564
  grep: fix CVE-2015-1345
  qt4: fix CVE issues
  libav: upgrade to 9.18
  libav: add recipe for 11 release series

 .../grep/grep/grep-fix-CVE-2015-1345.patch         | 154 +++++++++++++++++++++
 meta/recipes-extended/grep/grep_2.21.bb            |   3 +-
 meta/recipes-multimedia/libav/libav.inc            |   2 -
 .../libav/libav/libav-fix-CVE-2014-9676.patch      |  98 +++++++++++++
 meta/recipes-multimedia/libav/libav_11.3.bb        |   4 +
 meta/recipes-multimedia/libav/libav_9.16.bb        |   4 -
 meta/recipes-multimedia/libav/libav_9.18.bb        |   6 +
 meta/recipes-qt/qt4/qt4-4.8.6.inc                  |   2 +
 ...Fixes-crash-in-bmp-and-ico-image-decoding.patch |  71 ++++++++++
 .../0036-Fixes-crash-in-gif-image-decoder.patch    |  39 ++++++
 .../gpgme-1.4.3/gpgme-fix-CVE-2014-3564.patch      |  56 ++++++++
 meta/recipes-support/gpgme/gpgme_1.4.3.bb          |   4 +-
 12 files changed, 435 insertions(+), 8 deletions(-)
 create mode 100644 meta/recipes-extended/grep/grep/grep-fix-CVE-2015-1345.patch
 create mode 100644 meta/recipes-multimedia/libav/libav/libav-fix-CVE-2014-9676.patch
 create mode 100644 meta/recipes-multimedia/libav/libav_11.3.bb
 delete mode 100644 meta/recipes-multimedia/libav/libav_9.16.bb
 create mode 100644 meta/recipes-multimedia/libav/libav_9.18.bb
 create mode 100644 meta/recipes-qt/qt4/qt4-4.8.6/0035-Fixes-crash-in-bmp-and-ico-image-decoding.patch
 create mode 100644 meta/recipes-qt/qt4/qt4-4.8.6/0036-Fixes-crash-in-gif-image-decoder.patch
 create mode 100644 meta/recipes-support/gpgme/gpgme-1.4.3/gpgme-fix-CVE-2014-3564.patch

-- 
1.9.1



             reply	other threads:[~2015-05-28  1:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28  1:26 Kai Kang [this message]
2015-05-28  1:26 ` [PATCH 1/5] gpgme: fix CVE-2014-3564 Kai Kang
2015-05-28  1:26 ` [PATCH 2/5] grep: fix CVE-2015-1345 Kai Kang
2015-05-28  1:26 ` [PATCH 3/5] qt4: fix CVE issues Kai Kang
2015-05-28  6:12   ` Alexander Kanavin
2015-05-29  1:26     ` Kang Kai
2015-05-28  1:26 ` [PATCH 4/5] libav: upgrade to 9.18 Kai Kang
2015-05-28  7:14   ` Jussi Kukkonen
2015-05-28  8:18     ` Kang Kai
2015-05-28  8:38       ` Jussi Kukkonen
2015-05-28  8:47       ` Martin Jansa
2015-05-29  1:36         ` Kang Kai
2015-05-29 15:28           ` Paul Eggleton
2015-05-29 22:24             ` Phil Blundell
2015-05-30 13:17               ` Bernhard Reutner-Fischer
2015-05-28  1:26 ` [PATCH 5/5] libav: add recipe for 11 release series Kai Kang

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=cover.1432775689.git.kai.kang@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    /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