From: David Howells <dhowells@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org,
keyrings@linux-nfs.org, linux-kernel@vger.kernel.org,
dmitry.kasatkin@intel.com, zohar@linux.vnet.ibm.com,
arjan@linux.intel.com, alan@lxorguk.ukuu.org.uk
Subject: Re: [GIT PULL] Crypto keys and module signing
Date: Fri, 09 Dec 2011 09:17:33 +0000 [thread overview]
Message-ID: <2409.1323422253@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1112091505010.20839@tundra.namei.org>
James Morris <jmorris@namei.org> wrote:
> > Could you pull my module signing code into the security tree? The patches can
> > be viewed here:
>
> I'm getting this build error:
>
> make[1]: *** No rule to make target `kernel.pub', needed by
> `kernel/modsign-pubkey.o'. Stop.
If you turn module signing on, you have to supply keys for it to sign things
with and to later verify the signature...
I wonder what the best way to deal with that is... I guess make allyesconfig
and make allmodconfig are going to break otherwise.
David
next prev parent reply other threads:[~2011-12-09 9:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 14:47 [GIT PULL] Crypto keys and module signing David Howells
2011-12-09 4:05 ` James Morris
2011-12-09 9:17 ` David Howells [this message]
2011-12-09 9:35 ` James Morris
2011-12-09 14:20 ` Arjan van de Ven
2011-12-09 14:31 ` James Morris
2011-12-09 18:06 ` David Howells
2011-12-09 18:18 ` Arjan van de Ven
2011-12-09 18:47 ` David Howells
2011-12-09 18:49 ` Arjan van de Ven
2011-12-09 18:59 ` David Howells
2011-12-09 19:41 ` [Keyrings] " Daniel Kahn Gillmor
2011-12-10 9:49 ` Geert Uytterhoeven
2011-12-10 11:42 ` Arkadiusz Miśkiewicz
2011-12-10 18:54 ` Arjan van de Ven
2011-12-10 12:50 ` David Howells
2011-12-12 14:12 ` Nick Bowler
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=2409.1323422253@redhat.com \
--to=dhowells@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@linux.intel.com \
--cc=dmitry.kasatkin@intel.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.com \
/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).