From: Armin Kuster <akuster808@gmail.com>
To: akuster@mvista.com, openembedded-core@lists.openembedded.org
Subject: [PATCH 0/7] Jethro pull request #2
Date: Tue, 20 Sep 2016 12:12:30 -0700 [thread overview]
Message-ID: <cover.1474398462.git.akuster@mvista.com> (raw)
From: Armin Kuster <akuster@mvista.com>
please consider these changes for Jethro
Similar fixes for krogoth are in my staging branch
The following changes since commit 6f0350d1cbf5829bfbaa3a43227f8d564903743a:
wget: Security fix CVE-2016-4971 (2016-09-17 22:33:07 -0700)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib akuster/jethro-next
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=akuster/jethro-next
Armin Kuster (7):
qemu: Security Fix CVE-2016-3710
qemu: Security Fix CVE-2016-3712
qemu: Security fix CVE-2016-4439
qemu: Security fix CVE-2016-6351
qemu: Security fix for CVE-2016-4002
qemu: Secuirty fix for CVE-2016-5403
util-linux: Security fix for CVE-2016-5011
.../util-linux/util-linux/CVE-2016-5011.patch | 59 +++++++++
.../util-linux/util-linux/CVE-2016-5011_p2.patch | 91 ++++++++++++++
meta/recipes-core/util-linux/util-linux_2.26.2.bb | 2 +
.../recipes-devtools/qemu/qemu/CVE-2016-3710.patch | 112 +++++++++++++++++
.../qemu/qemu/CVE-2016-3712_p1.patch | 73 ++++++++++++
.../qemu/qemu/CVE-2016-3712_p2.patch | 132 +++++++++++++++++++++
.../qemu/qemu/CVE-2016-3712_p3.patch | 34 ++++++
.../qemu/qemu/CVE-2016-3712_p4.patch | 80 +++++++++++++
.../recipes-devtools/qemu/qemu/CVE-2016-4002.patch | 39 ++++++
.../recipes-devtools/qemu/qemu/CVE-2016-4439.patch | 46 +++++++
.../recipes-devtools/qemu/qemu/CVE-2016-5403.patch | 67 +++++++++++
.../qemu/qemu/CVE-2016-6351_p1.patch | 75 ++++++++++++
.../qemu/qemu/CVE-2016-6351_p2.patch | 60 ++++++++++
meta/recipes-devtools/qemu/qemu_2.4.0.bb | 10 ++
14 files changed, 880 insertions(+)
create mode 100644 meta/recipes-core/util-linux/util-linux/CVE-2016-5011.patch
create mode 100644 meta/recipes-core/util-linux/util-linux/CVE-2016-5011_p2.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-3710.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-3712_p1.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-3712_p2.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-3712_p3.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-3712_p4.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-4002.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-4439.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-5403.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-6351_p1.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-6351_p2.patch
--
2.7.4
next reply other threads:[~2016-09-20 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 19:12 Armin Kuster [this message]
2016-09-23 17:23 ` [PATCH 0/7] Jethro pull request #2 akuster808
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.1474398462.git.akuster@mvista.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.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