From: Kai Kang <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Upgrade libav and fix one qemu cve issue
Date: Tue, 26 May 2015 15:14:42 +0800 [thread overview]
Message-ID: <cover.1432624313.git.kai.kang@windriver.com> (raw)
The following changes since commit 971ce829df02cf6970d2a4af377704b8930feee9:
bitbake: data: Move warning code to the first loop for performance (2015-05-25 09:00:58 +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 (2):
qemu: fix CVE-2015-3456
libav: upgrade to 9.18
.../qemu/qemu/qemu-CVE-2015-3456.patch | 92 ++++++++++++++++++++
meta/recipes-devtools/qemu/qemu_2.3.0.bb | 1 +
meta/recipes-multimedia/libav/libav.inc | 2 -
.../libav/libav/libav-fix-CVE-2014-9676.patch | 98 ++++++++++++++++++++++
meta/recipes-multimedia/libav/libav_9.16.bb | 4 -
meta/recipes-multimedia/libav/libav_9.18.bb | 6 ++
6 files changed, 197 insertions(+), 6 deletions(-)
create mode 100644 meta/recipes-devtools/qemu/qemu/qemu-CVE-2015-3456.patch
create mode 100644 meta/recipes-multimedia/libav/libav/libav-fix-CVE-2014-9676.patch
delete mode 100644 meta/recipes-multimedia/libav/libav_9.16.bb
create mode 100644 meta/recipes-multimedia/libav/libav_9.18.bb
--
1.9.1
next reply other threads:[~2015-05-26 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 7:14 Kai Kang [this message]
2015-05-26 7:14 ` [PATCH 1/2] qemu: fix CVE-2015-3456 Kai Kang
2015-05-26 7:14 ` [PATCH 2/2] libav: upgrade to 9.18 Kai Kang
2015-05-27 1:24 ` Randy MacLeod
2015-05-27 1:59 ` Kang Kai
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.1432624313.git.kai.kang@windriver.com \
--to=kai.kang@windriver.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