All of lore.kernel.org
 help / color / mirror / Atom feed
From: "ito-yuichi@fujitsu.com" <ito-yuichi@fujitsu.com>
To: 'Khem Raj' <raj.khem@gmail.com>,
	"openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [PATCH] cve-check: Add allowlist that is same function of whitelist.
Date: Wed, 23 Jun 2021 00:19:50 +0000	[thread overview]
Message-ID: <TYCPR01MB55990300583DF9F78FE774B28F089@TYCPR01MB5599.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <ffe8bb78-c56b-08de-dfab-77ef8c89c6e6@gmail.com>

Hi Khem,

Sorry, I mistook send mailing list, and thank you for your advice.

> -----Original Message-----
> From: Khem Raj <raj.khem@gmail.com>
> Sent: Wednesday, June 23, 2021 1:35 AM
> To: Ito, Yuichi/伊藤 有一 <ito-yuichi@fujitsu.com>;
> openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] [PATCH] cve-check: Add allowlist that is same function of
> whitelist.
> 
> Thanks for the patch, you need to send to oe-core mailing list since this class
> is part of core metadata.
> 
> On 6/22/21 1:29 AM, 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>
> > ---
> >   meta/classes/cve-check.bbclass | 3 ++-
> >   1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/classes/cve-check.bbclass
> > b/meta/classes/cve-check.bbclass index 112ee3379d..5e3441a783 100644
> > --- a/meta/classes/cve-check.bbclass
> > +++ b/meta/classes/cve-check.bbclass
> > @@ -52,6 +52,7 @@ CVE_CHECK_PN_WHITELIST ?= ""
> >   # CVE_CHECK_WHITELIST = 'CVE-2014-2524 CVE-2018-1234'
> >   #
> >   CVE_CHECK_WHITELIST ?= ""
> > +CVE_CHECK_ALLOWLIST ?= ""
> >
> >   # Layers to be excluded
> >   CVE_CHECK_LAYER_EXCLUDELIST ??= ""
> > @@ -238,7 +239,7 @@ def check_cves(d, patched_cves):
> >       old_cve_whitelist =  d.getVar("CVE_CHECK_CVE_WHITELIST")
> >       if old_cve_whitelist:
> >           bb.warn("CVE_CHECK_CVE_WHITELIST is deprecated, please
> use CVE_CHECK_WHITELIST.")
> > -    cve_whitelist = d.getVar("CVE_CHECK_WHITELIST").split()
> > +    cve_whitelist = d.getVar("CVE_CHECK_ALLOWLIST").split() +
> > + d.getVar("CVE_CHECK_WHITELIST").split()
> >
> >       import sqlite3
> >       db_file = d.expand("file:${CVE_CHECK_DB_FILE}?mode=ro")
> >
> >
> >
> > 
> >

      reply	other threads:[~2021-06-23  0:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22  8:29 [PATCH] cve-check: Add allowlist that is same function of whitelist ito-yuichi
2021-06-22 16:35 ` [oe] " Khem Raj
2021-06-23  0:19   ` 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=TYCPR01MB55990300583DF9F78FE774B28F089@TYCPR01MB5599.jpnprd01.prod.outlook.com \
    --to=ito-yuichi@fujitsu.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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 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.