From: akuster808 <akuster808@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Armin Kuster <akuster@mvista.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Several Glibc security fixes
Date: Thu, 23 Nov 2017 08:16:22 -0800 [thread overview]
Message-ID: <40240a76-a59f-b721-2445-e70be9f047ea@gmail.com> (raw)
In-Reply-To: <CAJTo0Larccb=6j_AgMpMpxtSDkUCSCLzC3HDJ12rqk=9_ybMdQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On 11/23/2017 04:00 AM, Burton, Ross wrote:
> On 23 November 2017 at 03:52, Armin Kuster <akuster808@gmail.com
> <mailto:akuster808@gmail.com>> wrote:
>
> The pending 2.27 update does not need these. Only apply if that
> update is delayed too long.
>
>
> I don't see a pending 2.27 update, just a 2.26 update (to
> 77f921dac17c5fa99bd9e926d926c327982895f7). Is there a patch I'm missing?
I was hoping, would have made things easier.. so how do we plan on
disgusting between the two 2.26 versions ?? The CVE checker wont be able
too.
its possible this set of patchs may be different for the pending merge.
- armin
>
> Ross
[-- Attachment #2: Type: text/html, Size: 2001 bytes --]
next prev parent reply other threads:[~2017-11-23 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 3:52 [PATCH 0/3] Several Glibc security fixes Armin Kuster
2017-11-23 3:52 ` [PATCH 1/3] glibc: Security fix CVE-2017-15670 Armin Kuster
2017-11-23 3:52 ` [PATCH 2/3] glibc: Security fix CVE-2017-15671 Armin Kuster
2017-11-23 3:52 ` [PATCH 3/3] glibc: Security fix for CVE-2017-15804 Armin Kuster
2017-11-23 4:03 ` ✗ patchtest: failure for Several Glibc security fixes Patchwork
2017-11-23 12:00 ` [PATCH 0/3] " Burton, Ross
2017-11-23 16:16 ` akuster808 [this message]
2017-11-27 1:47 ` 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=40240a76-a59f-b721-2445-e70be9f047ea@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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