From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [jethro][PATCH] glibc CVE-2015-7547
Date: Thu, 18 Feb 2016 09:15:06 +0000 [thread overview]
Message-ID: <1455786906.3642.0.camel@linux.intel.com> (raw)
In-Reply-To: <1455734924-8832-1-git-send-email-akuster808@gmail.com>
On Wed, 2016-02-17 at 10:48 -0800, Armin Kuster wrote:
> This is being submitted to comply to Yocto compatability.
>
> Master is affected but waiting for 2.23 to be merged before sending
> patches.
I plan to backport this to fido as soon as it's on a branch I can
cherry-pick from.
Regards,
Joshua
>
> Armin Kuster (1):
> glibc: Security fix CVE-2015-7547
>
> meta/recipes-core/glibc/glibc/CVE-2015-7547.patch | 643
> ++++++++++++++++++++++
> meta/recipes-core/glibc/glibc_2.22.bb | 1 +
> 2 files changed, 644 insertions(+)
> create mode 100644 meta/recipes-core/glibc/glibc/CVE-2015-7547.patch
>
> --
> 2.3.5
>
prev parent reply other threads:[~2016-02-18 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 18:48 [jethro][PATCH] glibc CVE-2015-7547 Armin Kuster
2016-02-17 18:48 ` [jethro][PATCH] glibc: Security fix CVE-2015-7547 Armin Kuster
2016-02-18 9:15 ` Joshua G Lock [this message]
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=1455786906.3642.0.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.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