linux-kernel - Re: [PATCH] IMA: Use the system trusted keyrings instead of .ima

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: <4392.1459959890@warthog.procyon.org.uk>
Date:	Wed, 06 Apr 2016 17:24:50 +0100
From:	David Howells <dhowells@...hat.com>
To:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
Cc:	dhowells@...hat.com, linux-security-module@...r.kernel.org,
	keyrings@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] IMA: Use the system trusted keyrings instead of .ima_mok (update)

Looking in digsig.c, I see:

	#ifdef CONFIG_INTEGRITY_TRUSTED_KEYRING
	static bool init_keyring __initdata = true;
	#else
	static bool init_keyring __initdata;
	#endif

Since this doesn't ever appear to be altered, should integrity_init_keyring()
just be made conditionally compiled?

David