linux-kernel - Re: [RFC PATCH 18/20] IMA: Use the system blacklist keyring [ver #2]

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: <1455884186.2906.104.camel@linux.vnet.ibm.com>
Date:	Fri, 19 Feb 2016 07:16:26 -0500
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	David Howells <dhowells@...hat.com>
Cc:	linux-security-module@...r.kernel.org, keyrings@...r.kernel.org,
	petkan@...-labs.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 18/20] IMA: Use the system blacklist keyring [ver #2]

On Fri, 2016-02-19 at 11:58 +0000, David Howells wrote:
> Mimi Zohar <zohar@...ux.vnet.ibm.com> wrote:
> 
> > As discussed, "restrict_link_by_system_trusted" is not enough.  The
> > certificate being added should be in a revoked list as well.
> 
> What do you mean be a "revoked list"?  There currently isn't such a beast in
> IMA.  The patches I've proposed should make the functionality available
> approximately the same as exists now.

Support for the IMA mok and blacklist keyrings are disabled by default.
Please don't make this the default, at least until we add the equivalent
of revoked certificates.  Refer to the "Re: How to add additional
blacklist entries?"  thread.

Mimi