All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "chet.ramey@case.edu" <chet.ramey@case.edu>,
	"richard.purdie@linuxfoundation.org"
	<richard.purdie@linuxfoundation.org>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"De.Huo@windriver.com" <De.Huo@windriver.com>,
	"preid@electromag.com.au" <preid@electromag.com.au>,
	 "akuster808@gmail.com" <akuster808@gmail.com>
Subject: Re: bash: Fix CVE-2019-18276
Date: Tue, 18 Feb 2020 15:43:50 +0000	[thread overview]
Message-ID: <41e8a2902bc8594a17f0afa1744f04a6facd5316.camel@intel.com> (raw)
In-Reply-To: <9b99752af2094590137fdaacf6668f170b34158c.camel@linuxfoundation.org>

On Tue, 2020-02-18 at 15:35 +0000, Richard Purdie wrote:
> On Tue, 2020-02-18 at 10:28 -0500, Chet Ramey wrote:
> > On 2/17/20 9:46 PM, Huo, De wrote:
> > >  I applied the patch to fix CVE defect CVE-2019-18276.
> > 
> > That's not exactly an answer to the question of who produced the
> > patch.
> > If that patch is the one causing failures when it's applied,
> > doesn't it
> > make sense to go back to the person who produced it and ask them to
> > update it if necessary?
> 
> Its likely a general CVE patch where both configure and configure.ac
> are patched. For OE, we can drop the configure part since we
> reautoconf
> the code. Its therefore the OE port of the patch which is likely at
> fault.
> 
> Someone just needs to remove that section of the patch.

There are other issues with this patch which should also be fixed I
think. It has been marked as a Backport while it is not one. The patch
includes changes that are irrelevant to the CVE. And, it should have
gone to master first.

Thanks,

Anuj

  reply	other threads:[~2020-02-18 15:43 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 [this message]
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
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=41e8a2902bc8594a17f0afa1744f04a6facd5316.camel@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=De.Huo@windriver.com \
    --cc=akuster808@gmail.com \
    --cc=chet.ramey@case.edu \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=preid@electromag.com.au \
    --cc=richard.purdie@linuxfoundation.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.