From: Jarkko Sakkinen <jarkko@kernel.org>
To: Eric Snowberg <eric.snowberg@oracle.com>
Cc: dhowells@redhat.com, dwmw2@infradead.org,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
kanth.ghatraju@oracle.com, konrad.wilk@oracle.com
Subject: Re: [PATCH] certs: Reference revocation list for all keyrings
Date: Sat, 21 Jan 2023 03:21:27 +0000 [thread overview]
Message-ID: <Y8taNx6k/hQEeoGL@kernel.org> (raw)
In-Reply-To: <Y8taCkDpji8AGCUc@kernel.org>
On Sat, Jan 21, 2023 at 03:20:46AM +0000, Jarkko Sakkinen wrote:
> On Tue, Jan 17, 2023 at 12:15:06PM -0500, Eric Snowberg wrote:
> > Systems booted with shim have a Forbidden Signature Database called mokx.
> > During boot, hashes and certs contained within the mokx are loaded into the
> > blacklist keyring. When calling verify_pkcs7_message_sig the contents of
> > the blacklist keyring (or revocation list) are referenced when validating
> > keys on the platform keyring. Currently, when validating against the
> > secondary or builtin keyrings, the revocation list is not referenced. Move
> > up the check to allow the revocation list to be used with all keyrings,
> > including the secondary and builtin, allowing the system owner to take
> > corrective action should a vulnerability be found within keys contained
> > within either keyring.
> >
> > Signed-off-by: Eric Snowberg <eric.snowberg@oracle.com>
> > ---
> > certs/system_keyring.c | 12 ++++++------
> > 1 file changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/certs/system_keyring.c b/certs/system_keyring.c
> > index 5042cc54fa5e..865a0510fdeb 100644
> > --- a/certs/system_keyring.c
> > +++ b/certs/system_keyring.c
> > @@ -243,6 +243,12 @@ int verify_pkcs7_message_sig(const void *data, size_t len,
> > if (ret < 0)
> > goto error;
> >
> > + ret = is_key_on_revocation_list(pkcs7);
> > + if (ret != -ENOKEY) {
> > + pr_devel("PKCS#7 key is on revocation list\n");
> > + goto error;
> > + }
> > +
> > if (!trusted_keys) {
> > trusted_keys = builtin_trusted_keys;
> > } else if (trusted_keys == VERIFY_USE_SECONDARY_KEYRING) {
> > @@ -262,12 +268,6 @@ int verify_pkcs7_message_sig(const void *data, size_t len,
> > pr_devel("PKCS#7 platform keyring is not available\n");
> > goto error;
> > }
> > -
> > - ret = is_key_on_revocation_list(pkcs7);
> > - if (ret != -ENOKEY) {
> > - pr_devel("PKCS#7 platform key is on revocation list\n");
> > - goto error;
> > - }
> > }
> > ret = pkcs7_validate_trust(pkcs7, trusted_keys);
> > if (ret < 0) {
> > --
> > 2.27.0
> >
>
> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
Should I pick this?
BR, Jarkko
next prev parent reply other threads:[~2023-01-21 3:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 17:15 [PATCH] certs: Reference revocation list for all keyrings Eric Snowberg
2023-01-21 3:20 ` Jarkko Sakkinen
2023-01-21 3:21 ` Jarkko Sakkinen [this message]
2023-07-14 22:11 ` Mimi Zohar
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=Y8taNx6k/hQEeoGL@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=eric.snowberg@oracle.com \
--cc=kanth.ghatraju@oracle.com \
--cc=keyrings@vger.kernel.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox