From: Eric Snowberg <eric.snowberg@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: David Howells <dhowells@redhat.com>,
dwmw2@infradead.org,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
herbert@gondor.apana.org.au, davem@davemloft.net,
jmorris@namei.org, serge@hallyn.com, nayna@linux.ibm.com,
Mimi Zohar <zohar@linux.ibm.com>,
erichte@linux.ibm.com, mpe@ellerman.id.au,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v4] certs: Add EFI_CERT_X509_GUID support for dbx entries
Date: Fri, 15 Jan 2021 16:01:00 -0700 [thread overview]
Message-ID: <C40CED72-E44A-47DF-A965-04BFFE440B3A@oracle.com> (raw)
In-Reply-To: <0659f965b3321e793fee03136ae50cbbcd4a53bf.camel@HansenPartnership.com>
> On Jan 15, 2021, at 10:21 AM, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
>
> On Tue, 2020-09-15 at 20:49 -0400, Eric Snowberg wrote:
>> The Secure Boot Forbidden Signature Database, dbx, contains a list of
>> now revoked signatures and keys previously approved to boot with UEFI
>> Secure Boot enabled. The dbx is capable of containing any number of
>> EFI_CERT_X509_SHA256_GUID, EFI_CERT_SHA256_GUID, and
>> EFI_CERT_X509_GUID entries.
>>
>> Currently when EFI_CERT_X509_GUID are contained in the dbx, the
>> entries are skipped.
>>
>> Add support for EFI_CERT_X509_GUID dbx entries. When a
>> EFI_CERT_X509_GUID is found, it is added as an asymmetrical key to
>> the .blacklist keyring. Anytime the .platform keyring is used, the
>> keys in the .blacklist keyring are referenced, if a matching key is
>> found, the key will be rejected.
>>
>> Signed-off-by: Eric Snowberg <eric.snowberg@oracle.com>
>
> If you're using shim, as most of our users are, you have no access to
> dbx to blacklist certificates. Plus our security envelope includes the
> Mok variables, so you should also be paying attestion to MokListX (or
> it's RT equivalent: MokListXRT).
>
> If you add this to the patch, we get something that is mechanistically
> complete and which also allows users to add certs to their Mok
> blacklist.
That make sense. I’ll work on a patch to add this ability.
prev parent reply other threads:[~2021-01-15 23:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 0:49 [PATCH v4] certs: Add EFI_CERT_X509_GUID support for dbx entries Eric Snowberg
2020-09-16 18:09 ` Jarkko Sakkinen
2020-12-10 9:49 ` David Howells
2020-12-10 18:56 ` Eric Snowberg
2021-01-12 14:57 ` David Howells
2021-01-13 20:41 ` Jarkko Sakkinen
2021-01-14 0:11 ` Eric Snowberg
2021-01-15 9:15 ` Jarkko Sakkinen
2021-01-15 16:49 ` Eric Snowberg
2021-01-20 11:26 ` Jarkko Sakkinen
2021-01-20 22:13 ` Eric Snowberg
2021-01-21 0:36 ` Jarkko Sakkinen
2021-01-27 11:46 ` David Howells
2021-01-27 14:03 ` Mimi Zohar
2021-01-27 15:41 ` Eric Snowberg
2021-01-28 4:13 ` Nayna
2021-01-30 10:24 ` Jarkko Sakkinen
2021-01-29 23:27 ` Jarkko Sakkinen
2021-01-12 17:10 ` David Howells
2021-01-12 19:13 ` Eric Snowberg
2021-01-15 17:21 ` James Bottomley
2021-01-15 23:01 ` Eric Snowberg [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=C40CED72-E44A-47DF-A965-04BFFE440B3A@oracle.com \
--to=eric.snowberg@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=erichte@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nayna@linux.ibm.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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).