From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/4] Fix CVEs and qemu run-ptest script
Date: Thu, 10 Nov 2016 15:01:22 +0800 [thread overview]
Message-ID: <cover.1478760924.git.kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
The following changes since commit 09278be8c209976da03f63b5a956d212ac171317:
conf/distro/include/maintainers: move toolchain to Khem Raj (2016-11-09 12:20:48 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib kangkai/fixes-20161110
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/fixes-20161110
Kai Kang (4):
openssh: fix CVE-2016-8858
glibc: fix CVE-2016-6323
qemu: fix CVE-2016-7909
qemu: update run-ptest script
.../openssh/openssh/fix-CVE-2016-8858.patch | 39 ++++++++++++++++++
meta/recipes-connectivity/openssh/openssh_7.3p1.bb | 1 +
...k-__startcontext-as-.cantunwind-bug-20435.patch | 46 ++++++++++++++++++++++
meta/recipes-core/glibc/glibc_2.24.bb | 1 +
.../qemu/qemu/0004-fix-CVE-2016-7909.patch | 42 ++++++++++++++++++++
meta/recipes-devtools/qemu/qemu/run-ptest | 8 ++--
meta/recipes-devtools/qemu/qemu_2.7.0.bb | 1 +
7 files changed, 135 insertions(+), 3 deletions(-)
create mode 100644 meta/recipes-connectivity/openssh/openssh/fix-CVE-2016-8858.patch
create mode 100644 meta/recipes-core/glibc/glibc/0027-arm-mark-__startcontext-as-.cantunwind-bug-20435.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/0004-fix-CVE-2016-7909.patch
--
2.10.1
next reply other threads:[~2016-11-10 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 7:01 kai.kang [this message]
2016-11-10 7:01 ` [PATCH 1/4] openssh: fix CVE-2016-8858 kai.kang
2016-11-10 7:01 ` [PATCH 2/4] glibc: fix CVE-2016-6323 kai.kang
2016-11-10 7:01 ` [PATCH 3/4] qemu: fix CVE-2016-7909 kai.kang
2016-11-10 7:01 ` [PATCH 4/4] qemu: update run-ptest script 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.1478760924.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.