From: Jessica Yu <jeyu@kernel.org>
To: Ke Wu <mikewu@google.com>
Cc: David Howells <dhowells@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modsign: use all trusted keys to verify module signature
Date: Tue, 6 Nov 2018 13:35:40 +0100 [thread overview]
Message-ID: <20181106123540.GA20115@linux-8ccs> (raw)
In-Reply-To: <20181022222614.41016-1-mikewu@google.com>
+++ Ke Wu [22/10/18 15:26 -0700]:
>Make mod_verify_sig to use all trusted keys. This allows keys in
>secondary_trusted_keys to be used to verify PKCS#7 signature on a
>kernel module.
>
>Signed-off-by: Ke Wu <mikewu@google.com>
>---
> kernel/module_signing.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/kernel/module_signing.c b/kernel/module_signing.c
>index f2075ce8e4b3..a8b923ba1a39 100644
>--- a/kernel/module_signing.c
>+++ b/kernel/module_signing.c
>@@ -83,6 +83,6 @@ int mod_verify_sig(const void *mod, struct load_info *info)
> }
>
> return verify_pkcs7_signature(mod, modlen, mod + modlen, sig_len,
>- NULL, VERIFYING_MODULE_SIGNATURE,
>+ (void *)1UL, VERIFYING_MODULE_SIGNATURE,
> NULL, NULL);
> }
I've just stumbled on commit 817aef260037f ("Replace magic for trusting
the secondary keyring with #define"), so we should probably use
VERIFY_USE_SECONDARY_KEYRING in place of (void *)1UL.
Thanks,
Jessica
next prev parent reply other threads:[~2018-11-06 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 22:26 [PATCH] modsign: use all trusted keys to verify module signature Ke Wu
2018-10-30 19:11 ` Ke Wu
2018-10-31 9:36 ` Jessica Yu
2018-11-05 19:13 ` Ke Wu
2018-11-06 12:35 ` Jessica Yu [this message]
2018-11-06 23:21 ` [PATCH v2] " Ke Wu
2018-11-06 23:23 ` Ke Wu
2018-11-07 14:37 ` Jessica Yu
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=20181106123540.GA20115@linux-8ccs \
--to=jeyu@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikewu@google.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