linux-kernel - Re: [PATCH 1/1] Define CAP

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] [day] [month] [year] [list]

Date:	Mon, 29 Nov 2010 08:39:17 +1100 (EST)
From:	James Morris <jmorris@...ei.org>
To:	"Serge E. Hallyn" <serge@...lyn.com>
cc:	kernel list <linux-kernel@...r.kernel.org>,
	Eric Paris <eparis@...hat.com>,
	LSM <linux-security-module@...r.kernel.org>,
	Kees Cook <kees.cook@...onical.com>,
	Michael Kerrisk <mtk.manpages@...il.com>,
	Stephen Smalley <sds@...ho.nsa.gov>,
	"Christopher J. PeBenito" <cpebenito@...sys.com>
Subject: Re: [PATCH 1/1] Define CAP_SYSLOG

On Thu, 25 Nov 2010, Serge E. Hallyn wrote:

> Privileged syslog operations currently require CAP_SYS_ADMIN.  Split
> this off into a new CAP_SYSLOG privilege which we can sanely take away
> from a container through the capability bounding set.
> 
> With this patch, an lxc container can be prevented from messing with
> the host's syslog (i.e. dmesg -c).
> 
> Changelog: mar 12 2010: add selinux capability2:cap_syslog perm
> Changelog: nov 22 2010:
> 	. port to new kernel
> 	. add a WARN_ONCE if userspace isn't using CAP_SYSLOG

Applied with kernel version fix to:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next

-- 
James Morris
<jmorris@...ei.org>
--
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/