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.1112100128470.26387@tundra.namei.org>
Date:	Sat, 10 Dec 2011 01:31:49 +1100 (EST)
From:	James Morris <jmorris@...ei.org>
To:	Arjan van de Ven <arjan@...ux.intel.com>
cc:	David Howells <dhowells@...hat.com>,
	linux-security-module@...r.kernel.org, keyrings@...ux-nfs.org,
	linux-kernel@...r.kernel.org, dmitry.kasatkin@...el.com,
	zohar@...ux.vnet.ibm.com, alan@...rguk.ukuu.org.uk
Subject: Re: [GIT PULL] Crypto keys and module signing

On Fri, 9 Dec 2011, Arjan van de Ven wrote:

> the best way to deal is to have KBUILD generate a key on demand ;-)

Yes -- I'd like to see this code do something useful by default when 
enabled, so yes, create a local key during the build, possibly 
configurable via kconfig.

Is there any reason not to sign and verify kernel modules by default?



- James
-- 
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/