linux-kernel - Re: [RFC PATCH 12/12] IMA: Use the 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: <28505.1459519603@warthog.procyon.org.uk>
Date:	Fri, 01 Apr 2016 15:06:43 +0100
From:	David Howells <dhowells@...hat.com>
To:	unlisted-recipients:; (no To-header on input)
Cc:	dhowells@...hat.com, Mimi Zohar <zohar@...ux.vnet.ibm.com>,
	linux-security-module@...r.kernel.org, keyrings@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 12/12] IMA: Use the the system trusted keyrings instead of .ima_mok [ver #3]

David Howells <dhowells@...hat.com> wrote:

> The three choice options I implemented don't exactly provide new features.
> Firstly:
> 
> 	config IMA_LOAD_X509
> 
> allow keys to be loaded in at compile time,

Ah - I think I'm labouring under a slight misapprehension here.  IMA_LOAD_X509
doesn't load keys at compile time, but rather the kernel loads a file by name
when booting, right?

David