From: Luis Ressel <aranea@aixah.de>
To: <linux-kernel@vger.kernel.org>
Subject: Fw: [PATCH] Restrict read access to private module signing key
Date: Wed, 6 Jan 2016 01:06:19 +0100 [thread overview]
Message-ID: <20160106010619.31d72beb@gentp.lnet> (raw)
I forgot to CC this mailing list.
Begin forwarded message:
Date: Sat, 2 Jan 2016 16:13:50 +0100
From: Luis Ressel <aranea@aixah.de>
To: keyrings@vger.kernel.org
Cc: keyrings@linux-nfs.org, David Howells <dhowells@redhat.com>, David
Woodhouse <dwmw2@infradead.org> Subject: [PATCH] Restrict read access
to private module signing key
The autogenerated module signing key shouldn't be world-readable.
Signed-off-by: Luis Ressel <aranea@aixah.de>
---
certs/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/certs/Makefile b/certs/Makefile
index 28ac694..7f1f082 100644
--- a/certs/Makefile
+++ b/certs/Makefile
@@ -49,6 +49,8 @@ $(obj)/signing_key.pem: $(obj)/x509.genkey
@echo "### needs to be run as root, and uses a hardware random"
@echo "### number generator if one is available."
@echo "###"
+ touch $(obj)/signing_key.pem
+ chmod 0600 $(obj)/signing_key.pem
openssl req -new -nodes -utf8 -$(CONFIG_MODULE_SIG_HASH) -days
36500 \ -batch -x509 -config $(obj)/x509.genkey \
-outform PEM -out $(obj)/signing_key.pem \
--
2.6.4
reply other threads:[~2016-01-06 0:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160106010619.31d72beb@gentp.lnet \
--to=aranea@aixah.de \
--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;
as well as URLs for NNTP newsgroup(s).