linux-kernel - Re: [GIT PULL] Crypto keys and module signing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.00.1112092034140.25197@tundra.namei.org>
Date:	Fri, 9 Dec 2011 20:35:26 +1100 (EST)
From:	James Morris <jmorris@...ei.org>
To:	David Howells <dhowells@...hat.com>
cc:	linux-security-module@...r.kernel.org, keyrings@...ux-nfs.org,
	linux-kernel@...r.kernel.org, dmitry.kasatkin@...el.com,
	zohar@...ux.vnet.ibm.com, arjan@...ux.intel.com,
	alan@...rguk.ukuu.org.uk
Subject: Re: [GIT PULL] Crypto keys and module signing

On Fri, 9 Dec 2011, David Howells wrote:

> James Morris <jmorris@...ei.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.

Create a dummy key?


-- 
James Morris
<jmorris@...ei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/