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 for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1422607061.10643.21.camel@x220>
Date:	Fri, 30 Jan 2015 09:37:41 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	David Howells <dhowells@...hat.com>
Cc:	Valentin Rothberg <valentinrothberg@...il.com>,
	Jiri Kosina <jkosina@...e.cz>,
	Mimi Zohar <zohar@...ux.vnet.ibm.com>,
	Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
	James Morris <james.l.morris@...cle.com>,
	"Serge E. Hallyn" <serge@...lyn.com>,
	linux-ima-devel@...ts.sourceforge.net,
	linux-ima-user@...ts.sourceforge.net,
	linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: KEYS: KEYS_DEBUG_PROC_KEYS

Your commit dabd39cc2fb1 ("KEYS: Make /proc/keys unconditional if
CONFIG_KEYS=y") is included in today's linux-next (ie, next-20150130). I
noticed because a script I use to check linux-next spotted a minor
problem with it.

That commit removed the Kconfig symbol KEYS_DEBUG_PROC_KEYS. But it did
not remove a select for that symbol (see the entry for config
IMA_TRUSTED_KEYRING in security/integrity/ima/Kconfig). That select is
now a nop in linux-next. The commit suggests the trivial cleanup needed
here is to just remove that select. Is a patch to do that queued
somewhere?


Paul Bolle

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ