From: "Yu, Mingli" <Mingli.Yu@windriver.com>
To: "chet.ramey@case.edu" <chet.ramey@case.edu>,
"Mittal, Anuj" <anuj.mittal@intel.com>,
"richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"Huo, De" <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: Wed, 4 Mar 2020 01:14:27 +0000 [thread overview]
Message-ID: <E6F6D39CB834524199A3A6D928AB1465539F47F1@ALA-MBD.corp.ad.wrs.com> (raw)
In-Reply-To: <ee8f4da6-d917-4dab-d166-62bd7dcf6142@case.edu>
Thanks Chet very much for your confirmation!
If the commit fixs the CVE-2019-18276, why is it merged to the master branch?
Thanks,
Mingli
________________________________________
From: Chet Ramey [chet.ramey@case.edu]
Sent: Tuesday, March 03, 2020 9:55 PM
To: Yu, Mingli; Mittal, Anuj; richard.purdie@linuxfoundation.org; openembedded-core@lists.openembedded.org; Huo, De; preid@electromag.com.au; akuster808@gmail.com
Cc: chet.ramey@case.edu
Subject: Re: [OE-core] bash: Fix CVE-2019-18276
On 3/2/20 10:11 PM, Yu, Mingli wrote:
> Does https://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=951bdaad7a18cc0dc1036bba86b18b90874d39ff fix the issue reported in CVE-2019-18276? Could you help to provide some info here?
Yes, the changes from 6/27 fix the issue in the CVE.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
next prev parent reply other threads:[~2020-03-04 1:15 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
2020-03-04 1:16 ` Yu, Mingli
[not found] ` <ee8f4da6-d917-4dab-d166-62bd7dcf6142@case.edu>
2020-03-04 1:14 ` Yu, Mingli [this message]
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=E6F6D39CB834524199A3A6D928AB1465539F47F1@ALA-MBD.corp.ad.wrs.com \
--to=mingli.yu@windriver.com \
--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 \
--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.