From: Yusong Gao <a869920004@gmail.com>
To: mcgrof@kernel.org
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
a869920004@gmail.com
Subject: [PATCH v3] module: Add log info for verifying module signature
Date: Fri, 28 Jun 2024 10:39:23 +0000 [thread overview]
Message-ID: <20240628103923.1677347-1-a869920004@gmail.com> (raw)
Add log information in kernel-space when loading module failures.
Try to load the unsigned module and the module with bad signature
when set 1 to /sys/module/module/parameters/sig_enforce.
Unsigned module case:
(linux) insmod unsigned.ko
[ 18.714661] Loading of unsigned module is rejected
insmod: can't insert 'unsigned.ko': Key was rejected by service
(linux)
Bad signature module case:
(linux) insmod bad_signature.ko
insmod: can't insert 'bad_signature.ko': Key was rejected by service
(linux)
There have different logging behavior the bad signature case only log
in user-space, add log info for fatal errors in module_sig_check().
Signed-off-by: Yusong Gao <a869920004@gmail.com>
---
V3: Clarify the message type and the error code meaning.
V2: Change print level from notice to debug.
---
kernel/module/signing.c | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/kernel/module/signing.c b/kernel/module/signing.c
index a2ff4242e623..826cdab8e3e4 100644
--- a/kernel/module/signing.c
+++ b/kernel/module/signing.c
@@ -67,6 +67,31 @@ int mod_verify_sig(const void *mod, struct load_info *info)
NULL, NULL);
}
+static const char *mod_decode_error(int errno)
+{
+ char *errstr = "Unrecognized error";
+
+ switch (errno) {
+ case -ENOMEM:
+ errstr = "Out of memory";
+ break;
+ case -EINVAL:
+ errstr = "Invalid argument";
+ break;
+ case -EBADMSG:
+ errstr = "Invaild module signature format";
+ break;
+ case -EMSGSIZE:
+ errstr = "Message too long";
+ break;
+ case -EKEYREJECTED:
+ errstr = "Key was rejected by service";
+ break;
+ }
+
+ return errstr;
+}
+
int module_sig_check(struct load_info *info, int flags)
{
int err = -ENODATA;
@@ -113,6 +138,8 @@ int module_sig_check(struct load_info *info, int flags)
* unparseable signatures, and signature check failures --
* even if signatures aren't required.
*/
+ pr_debug("Verifying module signature failed: %s\n",
+ mod_decode_error(err));
return err;
}
--
2.34.1
next reply other threads:[~2024-06-28 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 10:39 Yusong Gao [this message]
2024-06-28 17:16 ` Luis Chamberlain
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=20240628103923.1677347-1-a869920004@gmail.com \
--to=a869920004@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@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
all inboxes | Powered by JetHome®