Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: bash: Fix CVE-2019-18276
Date: Tue, 3 Mar 2020 23:49:59 +0000	[thread overview]
Message-ID: <5cc81afa618ea969dc3d03f6e7ce356ec08e8efe.camel@intel.com> (raw)
In-Reply-To: <E6F6D39CB834524199A3A6D928AB1465539F327D@ALA-MBD.corp.ad.wrs.com>

On Tue, 2020-03-03 at 03:11 +0000, Yu, Mingli wrote:
> Hi Anuj,
> 
> I agree the Backport status is not accurate as the patch doesn't go
> to master branch, but why do you say the patch is irrelevant to the
> CVE-2019-18276, could you help to provide more info?

I didn't say that the patch was irrelevant to the CVE. I had said that
not all the changes were relevant. I believe the glob changes in the
patch were irrelevant. Those changes also introduced a failure in bash
ptests.

Thanks,

Anuj

  reply	other threads:[~2020-03-03 23:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <aa0bf5f6-aaf2-bfbf-6488-8d65cbe849f7@electromag.com.au>
     [not found] ` <4f09ab13-9571-3464-2fc3-334bc91b9c09@case.edu>
2020-02-18  2:46   ` bash: Fix CVE-2019-18276 Huo, De
     [not found]     ` <99d34efd-3a68-0b05-0e15-fbfd360a2f2a@case.edu>
2020-02-18 15:35       ` Richard Purdie
2020-02-18 15:43         ` Mittal, Anuj
2020-02-18 15:49           ` Richard Purdie
2020-02-19 15:46             ` akuster808
2020-02-19 18:55               ` Richard Purdie
2020-02-19  3:56           ` dhuo
2020-03-03  3:11           ` Yu, Mingli
2020-03-03 23:49             ` Mittal, Anuj [this message]
2020-03-04  1:16               ` Yu, Mingli
     [not found]             ` <ee8f4da6-d917-4dab-d166-62bd7dcf6142@case.edu>
2020-03-04  1:14               ` Yu, Mingli
2020-02-19  4:01       ` dhuo
2020-02-17  3:26 Phil Reid
2020-02-17  6:44 ` Andrey Zhizhikin
2020-02-17  9:55   ` Richard Purdie
2020-02-18  6:41     ` Phil Reid
2020-02-18  8:14       ` Richard Purdie

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=5cc81afa618ea969dc3d03f6e7ce356ec08e8efe.camel@intel.com \
    --to=anuj.mittal@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