From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
"Mittal, Anuj" <anuj.mittal@intel.com>,
"chet.ramey@case.edu" <chet.ramey@case.edu>,
"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>
Subject: Re: bash: Fix CVE-2019-18276
Date: Wed, 19 Feb 2020 18:55:04 +0000 [thread overview]
Message-ID: <c10081e8f424d555628a4bb323ee6c711953e34c.camel@linuxfoundation.org> (raw)
In-Reply-To: <c0c877fa-9d36-1019-0785-5c984970629e@gmail.com>
On Wed, 2020-02-19 at 07:46 -0800, akuster808 wrote:
>
> On 2/18/20 7:49 AM, Richard Purdie wrote:
> > On Tue, 2020-02-18 at 15:43 +0000, Mittal, Anuj wrote:
> > > On Tue, 2020-02-18 at 15:35 +0000, Richard Purdie wrote:
> > > >
> > > > 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.
> > I shall await guidance from you/Armin then.
>
> We should revert the commit. Ill send a patch.
Anuj sent it, I've merged it to zeus. Open questions:
Should we ship 3.0.2 rc2?
Did this patch cause this regression:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13795
Cheers,
Richard
next prev parent reply other threads:[~2020-02-19 18:55 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 [this message]
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=c10081e8f424d555628a4bb323ee6c711953e34c.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=De.Huo@windriver.com \
--cc=akuster808@gmail.com \
--cc=anuj.mittal@intel.com \
--cc=chet.ramey@case.edu \
--cc=openembedded-core@lists.openembedded.org \
--cc=preid@electromag.com.au \
/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.