linux-kernel - Re: [PATCH] syslog: check cap_syslog when dmesg

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: <20101208175316.GL5750@outflux.net>
Date:	Wed, 8 Dec 2010 09:53:16 -0800
From:	Kees Cook <kees.cook@...onical.com>
To:	"Serge E. Hallyn" <serge@...lyn.com>
Cc:	James Morris <jmorris@...ei.org>, Eric Paris <eparis@...hat.com>,
	Stephen Smalley <sds@...ho.nsa.gov>, dwalsh@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] syslog: check cap_syslog when dmesg_restrict

On Wed, Dec 08, 2010 at 03:19:01PM +0000, Serge E. Hallyn wrote:
> Eric Paris pointed out that it doesn't make sense to require
> both CAP_SYS_ADMIN and CAP_SYSLOG for certain syslog actions.
> So require CAP_SYSLOG, not CAP_SYS_ADMIN, when dmesg_restrict
> is set.
> 
> (I'm also consolidating the now common error path)
> 
> Signed-off-by: Serge E. Hallyn <serge.hallyn@...onical.com>

Acked-by: Kees Cook <kees.cook@...onical.com>

-- 
Kees Cook
Ubuntu Security Team
--
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/