From: "Chen-Yu Tsai (Moxa)" <wens@csie.org>
To: cip-dev@lists.cip-project.org
Cc: "SZ Lin (林上智)" <sz.lin@moxa.com>,
"Ben Hutchings" <ben.hutchings@codethink.co.uk>
Subject: Re: [cip-dev] [cip-kernel-sec 3/3] issues: fill in the description field of remaining CVEs
Date: Wed, 14 Oct 2020 12:21:37 +0800 [thread overview]
Message-ID: <CAGb2v66veK5kpCZD-h2b8qBJox_qpDXn7_WZeZisv25d5Wu0Kg@mail.gmail.com> (raw)
In-Reply-To: <OSBPR01MB2053976D2C2708EC5A906FDCD0050@OSBPR01MB2053.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
On Wed, Oct 14, 2020 at 12:16 PM Daniel Sangorrin
<daniel.sangorrin@toshiba.co.jp> wrote:
>
> Hello Chen-yu,
>
> Thanks for your check.
>
> > -----Original Message-----
> > From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Chen-Yu Tsai (Moxa)
> > Sent: Thursday, October 8, 2020 5:19 PM
> > To: cip-dev@lists.cip-project.org
> > Cc: SZ Lin (林上智) <sz.lin@moxa.com>; Ben Hutchings <ben.hutchings@codethink.co.uk>
> > Subject: Re: [cip-dev] [cip-kernel-sec 3/3] issues: fill in the description field of remaining CVEs
> >
> > On Fri, Sep 25, 2020 at 12:01 PM Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp> wrote:
> > >
> > > From: nguyen van hieu <hieu2.nguyenvan@toshiba.co.jp>
> > >
> > > I noticed that some issues have the description field empty when using
> > > the --show-description option.
> > >
> > > Signed-off-by: nguyen van hieu <hieu2.nguyenvan@toshiba.co.jp>
> > > Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
> >
> > Looks like all the new descriptions were copied from MITRE.
> >
> > Reviewed-by: Chen-Yu Tsai (Moxa) <wens@csie.org>
>
> Is there a problem with that?
> The MITRE license is included in the COPYING file as far as I know.
Not at all. I'm merely stating that the descriptions match a known source.
ChenYu
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5573): https://lists.cip-project.org/g/cip-dev/message/5573
Mute This Topic: https://lists.cip-project.org/mt/77073076/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-10-14 4:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 3:59 [cip-dev] improve show-description results Daniel Sangorrin
2020-09-25 3:59 ` [cip-dev] [cip-kernel-sec 1/3] report_affected: word-wrap for the 'description' Daniel Sangorrin
2020-10-08 7:58 ` Chen-Yu Tsai (Moxa)
2020-09-25 3:59 ` [cip-dev] [cip-kernel-sec 2/3] report_affected: Delete extra blank lines between CVEs Daniel Sangorrin
2020-10-08 7:59 ` Chen-Yu Tsai (Moxa)
2020-10-08 8:00 ` Chen-Yu Tsai (Moxa)
2020-09-25 3:59 ` [cip-dev] [cip-kernel-sec 3/3] issues: fill in the description field of remaining CVEs Daniel Sangorrin
2020-10-08 8:18 ` Chen-Yu Tsai (Moxa)
2020-10-14 4:16 ` Daniel Sangorrin
2020-10-14 4:21 ` Chen-Yu Tsai (Moxa) [this message]
2020-09-30 3:29 ` [cip-dev] improve show-description results Chen-Yu Tsai (Moxa)
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=CAGb2v66veK5kpCZD-h2b8qBJox_qpDXn7_WZeZisv25d5Wu0Kg@mail.gmail.com \
--to=wens@csie.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
--cc=sz.lin@moxa.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;
as well as URLs for NNTP newsgroup(s).