From: Luis Ressel <aranea@aixah.de>
To: keyrings@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
James Morris <jmorris@namei.org>
Subject: Re: [PATCH] Restrict read access to private module signing key
Date: Sun, 17 Jan 2016 00:02:26 +0100 [thread overview]
Message-ID: <20160117000226.493fa99f@gentp.lnet> (raw)
In-Reply-To: <1451747630-15940-1-git-send-email-aranea@aixah.de>
On Sat, 2 Jan 2016 16:13:50 +0100
Luis Ressel <aranea@aixah.de> wrote:
> 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 \
I've contributed this patch two weeks ago, but there hasn't been any
feedback and it hasn't been merged, either. It's the first kernel patch
I've submitted, so I don't know much about the procedures here. Could
someone please merge the patch or point out any problems with it?
Regards,
Luis Ressel
next parent reply other threads:[~2016-01-16 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1451747630-15940-1-git-send-email-aranea@aixah.de>
2016-01-16 23:02 ` Luis Ressel [this message]
2016-01-30 13:27 [PATCH] Restrict read access to private module signing key Luis Ressel
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=20160117000226.493fa99f@gentp.lnet \
--to=aranea@aixah.de \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--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