All of lore.kernel.org
 help / color / mirror / Atom feed
From: "ito-yuichi@fujitsu.com" <ito-yuichi@fujitsu.com>
To: 'akuster808' <akuster808@gmail.com>
Cc: 'Richard Purdie' <richard.purdie@linuxfoundation.org>,
	"'openembedded-core@lists.openembedded.org'"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] cve-check: Add allowlist that is same function of whitelist.
Date: Fri, 6 Aug 2021 08:38:15 +0000	[thread overview]
Message-ID: <TYCPR01MB5599F425D47902067C50F66E8FF39@TYCPR01MB5599.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TYCPR01MB559974130EF14CC85D5D621B8FE29@TYCPR01MB5599.jpnprd01.prod.outlook.com>

HI, Armin

Sorry to bother you again.
Could you please tell me what should I do for the variables to be approved in wiki?

Thanks,

Yuichi Ito

> -----Original Message-----
> From: Ito, Yuichi
> Sent: Tuesday, July 20, 2021 3:49 PM
> To: 'akuster808' <akuster808@gmail.com>
> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>;
> openembedded-core@lists.openembedded.org
> Subject: RE: [OE-core] [PATCH] cve-check: Add allowlist that is same
> function of whitelist.
> 
> HI, Armin
> 
> Thanks for information of wiki.
> I created account and add CVE_CHECK_WHITELIST in Variables.
> 
> According to this message, CVE_CHECK_PN_WHITELIST is deprecate and
> should remove it.
> https://lists.openembedded.org/g/openembedded-core/message/142505
> 
> Thanks,
> 
> Yuichi Ito
> 
> > -----Original Message-----
> > From: akuster808 <akuster808@gmail.com>
> > Sent: Tuesday, July 6, 2021 4:09 AM
> > To: Richard Purdie <richard.purdie@linuxfoundation.org>; Ito,
> > Yuichi/伊藤 有
> > 一 <ito-yuichi@fujitsu.com>;
> openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] [PATCH] cve-check: Add allowlist that is same
> > function of whitelist.
> >
> >
> >
> > On 6/26/21 3:04 AM, Richard Purdie wrote:
> > > On Wed, 2021-06-23 at 17:56 +0900, ito-yuichi@fujitsu.com wrote:
> > >> The Linux team plan to removed references to racially-charged
> > >> jargon from their code for more neutral and inclusive language.
> > >> So replace use of "whitelist" with "allowlist" in cve-check.
> > >>
> > >> First, we add CVE_CHECK_ALLOWLIST and it is considered patched as
> > >> well as CVE_CHECK_WHITELIST.
> > >> We plan to replace about other word later and eventualy, replace
> > >> all "whitelist" to "allowlist".
> > >>
> > >> Signed-off-by: Yuichi Ito <ito-yuichi@fujitsu.com>
> > > The TSC did discuss this and proposed a plan on how we should go
> > > about addressing these issues:
> > >
> > >
> >
> https://lists.openembedded.org/g/openembedded-architecture/topic/inclu
> > > sive_language_summary/75821819
> > >
> > > I appreciate this patch has good intent but I would really like to
> > > see a wider plan on how we address this rather than changing single
> > > variables piecemeal.
> > >
> > > For example we may want to standardise on the term "IGNORE" rather
> > > than "ALLOW" or even "FILTER" or "VERIFIED" or something more
> > > specific to the meaning of CVEs and CVE checking.
> > >
> > > There is an opportunity to try and make the metadata and variable
> > > names more consistent and understandable but if we just change
> > > single things at a time this opportunity would be missed.
> >
> > I have created a wiki page to collate our thoughts and agreements to
> > help us move foreword in a coherent manner to address renaming some
> > troubling variable names.
> > https://wiki.yoctoproject.org/wiki/Inclusive_language
> >
> > I logged some variable names along with a few renaming examples. Maybe
> > this can turn into a plan???
> >
> > Since it's a wiki, please edit accordingly.
> >
> > - armin
> >
> >
> > Cheers,
> > > Richard
> > >
> > >
> > > 
> > >


      parent reply	other threads:[~2021-08-06  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23  8:56 [PATCH] cve-check: Add allowlist that is same function of whitelist ito-yuichi
2021-06-26 10:04 ` [OE-core] " Richard Purdie
2021-06-29  6:47   ` ito-yuichi
2021-07-05 19:08   ` Armin Kuster
2021-07-20  6:48     ` ito-yuichi
2021-07-26  8:28       ` ito-yuichi
2021-08-06  8:38       ` ito-yuichi [this message]

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=TYCPR01MB5599F425D47902067C50F66E8FF39@TYCPR01MB5599.jpnprd01.prod.outlook.com \
    --to=ito-yuichi@fujitsu.com \
    --cc=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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.