From: Michal Marek <mmarek@suse.cz>
To: Abelardo Ricart III <aricart@memnix.com>
Cc: linux-kbuild@vger.kernel.org, David Howells <dhowells@redhat.com>,
keyrings@linux-nfs.org
Subject: Re: [PATCHv2 RFC 1/1] Explicit check for existing X.509 module signing keypair
Date: Mon, 13 Apr 2015 15:16:17 +0200 [thread overview]
Message-ID: <552BC1A1.7010504@suse.cz> (raw)
In-Reply-To: <1428626238.3789.0.camel@memnix.com>
Added David Howels and keyrings@linux-nfs.org to Cc
Michal
On 2015-04-10 02:37, Abelardo Ricart III wrote:
>
> The module-signing.txt documentation states that the kernel will use an existing
> x.509 key pair for module signing should they exist in the root of the source tree.
> However, user provided signing keys are unexpectedly overwritten during build if the
> last-modified times on the key pair are older than the "x509.genkey" target dependency.
> This fix stops this unexpected behavior, and warns if the key pair was not found.
>
> Signed-off-by: Abelardo Ricart III <aricart@memnix.com>
> ---
>
> diff --git a/kernel/Makefile b/kernel/Makefile
> index 1408b33..10c8df0 100644
> --- a/kernel/Makefile
> +++ b/kernel/Makefile
> @@ -168,7 +168,8 @@ ifndef CONFIG_MODULE_SIG_HASH
> $(error Could not determine digest type to use from kernel config)
> endif
>
> -signing_key.priv signing_key.x509: x509.genkey
> +signing_key.priv signing_key.x509: | x509.genkey
> + $(warning *** X.509 module signing key pair not found in root of source tree ***)
> @echo "###"
> @echo "### Now generating an X.509 key pair to be used for signing modules."
> @echo "###"
>
next prev parent reply other threads:[~2015-04-13 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 0:37 [PATCHv2 RFC 1/1] Explicit check for existing X.509 module signing keypair Abelardo Ricart III
2015-04-13 13:16 ` Michal Marek [this message]
2015-04-24 23:04 ` Abelardo Ricart III
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=552BC1A1.7010504@suse.cz \
--to=mmarek@suse.cz \
--cc=aricart@memnix.com \
--cc=dhowells@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.