[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <046773AE-687A-4924-8564-FDBBEEAB663F@oracle.com>
Date: Thu, 28 Jan 2021 18:56:16 -0700
From: Eric Snowberg <eric.snowberg@...cle.com>
To: David Howells <dhowells@...hat.com>
Cc: Nayna <nayna@...ux.vnet.ibm.com>, dwmw2@...radead.org,
Jarkko Sakkinen <jarkko@...nel.org>,
James.Bottomley@...senPartnership.com, masahiroy@...nel.org,
michal.lkml@...kovi.net, jmorris@...ei.org, serge@...lyn.com,
ardb@...nel.org, zohar@...ux.ibm.com, lszubowi@...hat.com,
javierm@...hat.com, keyrings@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH v5 1/4] certs: Add EFI_CERT_X509_GUID support for dbx
entries
> On Jan 28, 2021, at 8:58 AM, David Howells <dhowells@...hat.com> wrote:
>
> Nayna <nayna@...ux.vnet.ibm.com> wrote:
>
>> Thanks Eric for clarifying. I was confusing it with with the broader meaning
>> of revocation i.e. certificate revocation list. To avoid similar confusion in
>> the future, I wonder if we should call it as 'blocklist' or 'denylist' as
>> suggested in the document. This is to avoid conflicts with actual CRL support
>> if added in the future. I also wonder if we should add the clarification in
>> the patch description.
>
> Reject-list might be better.
As far as naming goes, I have no preference. If we can come to an agreement
on the name, I can change it if needed. Or David, if you want to pull it into
your tree and change the naming again, I’m fine with whatever you pick. Just
let me know how you would like to handle it.
Powered by blists - more mailing lists