[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090326132738.GB13639@us.ibm.com>
Date: Thu, 26 Mar 2009 08:27:38 -0500
From: "Serge E. Hallyn" <serue@...ibm.com>
To: Willy Tarreau <w@....eu>
Cc: mtk.manpages@...il.com, Stephen Smalley <sds@...ch.ncsc.mil>,
Andrew Morgan <morgan@...nel.org>,
linux-security-module@...r.kernel.org,
lkml <linux-kernel@...r.kernel.org>, linux-nfs@...r.kernel.org,
Igor Zhbanov <izh1979@...il.com>, stable@...nel.org,
linux-api@...r.kernel.org, Chris Wright <chrisw@...s-sol.org>
Subject: Re: [PATCH 2.4] CAP_FS_MASK: add CAP_LINUX_IMMUTABLE and CAP_MKNOD
Quoting Willy Tarreau (w@....eu):
> Hello,
>
> On Wed, Mar 25, 2009 at 12:39:54PM -0500, Serge E. Hallyn wrote:
> > When POSIX capabilities were introduced during the 2.1 Linux
> > cycle, the fs mask, which represents the capabilities which having
> > fsuid==0 is supposed to grant, did not include CAP_MKNOD and
> > CAP_LINUX_IMMUTABLE. However, before capabilities the privilege
> > to call these did in fact depend upon fsuid==0.
> >
> > This patch introduces those capabilities into the fsmask,
> > restoring the old behavior.
> >
> > See the thread starting at http://lkml.org/lkml/2009/3/11/157 for
> > reference.
>
> Thanks to Igor and you for fixing this. The impact did not appear
> obvious to me at first, to be honnest! I'm queuing the patch for
> next release.
>
> BTW, I've noticed your other patch for 2.2.26, but it's not worth
> wasting time on it, as 2.2 has remained unmaintained for years now
> and people are really discouraged from using it as many holes have
> never been fixed there.
>
> Cheers,
> Willy
Sounds good to me.
thanks,
-serge
--
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