From: Armin Kuster <akuster808@gmail.com>
To: akuster@mvista.com, openembedded-core@lists.openembedded.org,
liezhi.yang@windriver.com
Subject: [Jethro][PATCH 0/5] Jethro Pull request
Date: Fri, 19 Feb 2016 06:48:20 -0800 [thread overview]
Message-ID: <cover.1455892758.git.akuster@mvista.com> (raw)
From: Armin Kuster <akuster@mvista.com>
Please consider these security fixes for Jethro next. Some maybe a resend as I don't know if they are queued anywhere.
Master has these in some for or another.
The following changes since commit ae57ea03c6a41f2e3b61e0c157e32ca7df7b3c4b:
libbsd: Security fix CVE-2016-2090 (2016-02-18 10:57:11 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib akuster/jethro_cve_fixes
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akuster/jethro_cve_fixes
Armin Kuster (5):
uclibc: Security fix CVE-2016-2224
uclibc: Security fix CVE-2016-2225
libgcrypt: Security fix CVE-2015-7511
qemu: Security fix CVE-2016-2197
qemu: Security fix CVE-2016-2198
meta/recipes-core/uclibc/uclibc-git.inc | 2 +
.../uclibc/uclibc-git/CVE-2016-2224.patch | 49 +++++
.../uclibc/uclibc-git/CVE-2016-2225.patch | 32 +++
.../recipes-devtools/qemu/qemu/CVE-2016-2197.patch | 59 +++++
.../recipes-devtools/qemu/qemu/CVE-2016-2198.patch | 45 ++++
meta/recipes-devtools/qemu/qemu_2.4.0.bb | 2 +
.../libgcrypt/files/CVE-2015-7511_1.patch | 245 +++++++++++++++++++++
.../libgcrypt/files/CVE-2015-7511_2.patch | 55 +++++
meta/recipes-support/libgcrypt/libgcrypt_1.6.3.bb | 4 +
9 files changed, 493 insertions(+)
create mode 100644 meta/recipes-core/uclibc/uclibc-git/CVE-2016-2224.patch
create mode 100644 meta/recipes-core/uclibc/uclibc-git/CVE-2016-2225.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-2197.patch
create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2016-2198.patch
create mode 100644 meta/recipes-support/libgcrypt/files/CVE-2015-7511_1.patch
create mode 100644 meta/recipes-support/libgcrypt/files/CVE-2015-7511_2.patch
--
2.3.5
reply other threads:[~2016-02-19 14:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1455892758.git.akuster@mvista.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=liezhi.yang@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.