Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753848Ab0K1Vjf (ORCPT ); Sun, 28 Nov 2010 16:39:35 -0500 Received: from tundra.namei.org ([65.99.196.166]:54299 "EHLO tundra.namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751603Ab0K1Vje (ORCPT ); Sun, 28 Nov 2010 16:39:34 -0500 Date: Mon, 29 Nov 2010 08:39:17 +1100 (EST) From: James Morris To: "Serge E. Hallyn" cc: kernel list , Eric Paris , LSM , Kees Cook , Michael Kerrisk , Stephen Smalley , "Christopher J. PeBenito" Subject: Re: [PATCH 1/1] Define CAP_SYSLOG In-Reply-To: <20101125171132.GA25703@mail.hallyn.com> Message-ID: References: <20101125171132.GA25703@mail.hallyn.com> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 932 Lines: 25 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/