linux-kernel - Re: [PATCH] MODSIGN: /proc/keys is not unconditionally available

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: <11415.1421965730@warthog.procyon.org.uk>
Date:	Thu, 22 Jan 2015 22:28:50 +0000
From:	David Howells <dhowells@...hat.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	dhowells@...hat.com, Rusty Russell <rusty@...tcorp.com.au>,
	Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH] MODSIGN: /proc/keys is not unconditionally available

Jiri Kosina <jkosina@...e.cz> wrote:

> > Documentation/module-signing.txt file is referring to /proc/keys file in 
> > order to view all keys contained in the kernel's keyring. That file is not 
> > universally avialble when CONFIG_KEYS is enabled, which is confusing. The 
> > fact that the option needed for this procfs interface to exist contains 
> > "_DEBUG_" in its name makes it even more confusing. Document this fact.
> > 
> > Signed-off-by: Jiri Kosina <jkosina@...e.cz>
> 
> Noone complained, but it doesn't seem to have made its way to linux-next 
> either. I am now pushing it out to trivial.git.

Sorry, I should've dealt with this.  What we actually need to do is make
/proc/keys unconditional as it's used by libkeyutils.

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