From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4][fido] Glibc security fixes
Date: Mon, 25 Jan 2016 11:34:48 -0800 [thread overview]
Message-ID: <cover.1453750404.git.akuster808@gmail.com> (raw)
noticed this did not hit the patchwork. resending.
Please consider these for the next fido update.
The following changes since commit 9845a542a76156adb5aef6fd33ad5bc5777acf64:
openssh: CVE-2016-077x (2016-01-20 17:08:30 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib akuster/fido_glibc_cve_fixes
http://git.yoctoproject.org/cgit.cgi//log/?h=akuster/fido_glibc_cve_fixes
Armin Kuster (4):
glibc: CVE-2015-8777
glibc: CVE-2015-8779
glibc: CVE-2015-9761
glibc: CVE_2015-8776
meta/recipes-core/glibc/glibc/CVE-2015-8776.patch | 176 +++
meta/recipes-core/glibc/glibc/CVE-2015-8777.patch | 143 ++
meta/recipes-core/glibc/glibc/CVE-2015-8779.patch | 282 ++++
meta/recipes-core/glibc/glibc/CVE-2015-9761.patch | 1452 +++++++++++++++++++++
meta/recipes-core/glibc/glibc_2.21.bb | 4 +
5 files changed, 2057 insertions(+)
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2015-8776.patch
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2015-8777.patch
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2015-8779.patch
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2015-9761.patch
--
2.3.5
next reply other threads:[~2016-01-25 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 19:34 Armin Kuster [this message]
2016-01-25 19:34 ` [PATCH 1/4] glibc: CVE-2015-8777 Armin Kuster
2016-01-25 19:34 ` [PATCH 2/4] glibc: CVE-2015-8779 Armin Kuster
2016-01-25 19:34 ` [PATCH 3/4] glibc: CVE-2015-9761 Armin Kuster
2016-01-25 19:34 ` [PATCH 4/4] glibc: CVE_2015-8776 Armin Kuster
2016-01-25 20:00 ` [PATCH 0/4][fido] Glibc security fixes Khem Raj
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.1453750404.git.akuster808@gmail.com \
--to=akuster808@gmail.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.