From: Rusty Russell <rusty@rustcorp.com.au>
To: Chris Samuel <chris@csamuel.org>,
linux-kernel@vger.kernel.org, dhowells@redhat.com,
Josh Boyer <jwboyer@gmail.com>
Subject: Re: [PATCH] MODSIGN: Warn when module signature checking fails
Date: Mon, 21 Jan 2013 10:06:11 +1030 [thread overview]
Message-ID: <87a9s3xw9g.fsf@rustcorp.com.au> (raw)
In-Reply-To: <50F67D75.9080508@csamuel.org>
Chris Samuel <chris@csamuel.org> writes:
> /* Please CC me, I'm not on LKML */
>
> * Reworked from the original patch based on feedback from Josh Boyer
> * (putting the code in load_module()) and Rusty Russel (use
> * KERN_NOTICE). Extended to cover the other failure modes.
We have errnos for a reason; let's not pollute the kernel logs. That's
a userspace job.
> @@ -3115,8 +3130,10 @@ static int load_module(struct load_info *info,
> const char __user *uargs,
> #ifdef CONFIG_MODULE_SIG
> mod->sig_ok = info->sig_ok;
> - if (!mod->sig_ok)
> + if (!mod->sig_ok) {
> + printk_once(KERN_NOTICE "Module verification failed: signature and/or
> required key missing - tainting kernel\n");
> add_taint_module(mod, TAINT_FORCED_MODULE);
> + }
This part is OK, but I'll add mod->name to the printk.
How's this:
module: printk message when module signature fail taints kernel.
Reported-by: Chris Samuel <chris@csamuel.org>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
diff --git a/kernel/module.c b/kernel/module.c
index ec535aa..e095e19 100644
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -3169,8 +3169,12 @@ again:
#ifdef CONFIG_MODULE_SIG
mod->sig_ok = info->sig_ok;
- if (!mod->sig_ok)
+ if (!mod->sig_ok) {
+ printk_once(KERN_NOTICE
+ "%s: module verification failed: signature and/or"
+ " required key missing - tainting kernel\n");
add_taint_module(mod, TAINT_FORCED_MODULE);
+ }
#endif
/* Now module is in final location, initialize linked lists, etc. */
next prev parent reply other threads:[~2013-01-21 0:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 10:14 [PATCH] MODSIGN: Warn when module signature checking fails Chris Samuel
2013-01-20 23:36 ` Rusty Russell [this message]
2013-01-21 0:34 ` Stephen Rothwell
2013-01-21 1:41 ` Rusty Russell
2013-01-21 22:54 ` Chris Samuel
2013-01-22 4:24 ` Rusty Russell
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=87a9s3xw9g.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=chris@csamuel.org \
--cc=dhowells@redhat.com \
--cc=jwboyer@gmail.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