From: Valdis.Kletnieks@vt.edu
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
mtk.manpages@gmail.com, Stephen Smalley <sds@epoch.ncsc.mil>,
Andrew Morgan <morgan@kernel.org>,
linux-security-module@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org, Igor Zhbanov <izh1979@gmail.com>,
"J. Bruce Fields" <bfields@citi.umich.edu>,
stable@kernel.org, linux-api@vger.kernel.org,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH] add some long-missing capabilities to fs_mask
Date: Mon, 13 Apr 2009 17:03:28 -0400 [thread overview]
Message-ID: <13502.1239656608@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 13 Apr 2009 09:56:14 CDT." <20090413145614.GA15342@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
On Mon, 13 Apr 2009 09:56:14 CDT, "Serge E. Hallyn" said:
> 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.
Wow. How did this manage to stay un-noticed for this long?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-04-13 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 14:56 Serge E. Hallyn
2009-04-13 21:03 ` Valdis.Kletnieks [this message]
2009-04-13 21:33 ` Linus Torvalds
2009-04-13 21:50 ` Serge E. Hallyn
-- strict thread matches above, loose matches on Subject: below --
2009-03-23 22:46 Serge E. Hallyn
2009-03-20 18:37 Serge E. Hallyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13502.1239656608@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=bfields@citi.umich.edu \
--cc=chrisw@sous-sol.org \
--cc=izh1979@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=sds@epoch.ncsc.mil \
--cc=serue@us.ibm.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®