From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Chris Friedhoff <chris@friedhoff.org>,
"Serge E. Hallyn" <serue@us.ibm.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Stephen Smalley <sds@tycho.nsa.gov>,
James Morris <jmorris@namei.org>,
Chris Wright <chrisw@sous-sol.org>,
KaiGai Kohei <kaigai@kaigai.gr.jp>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: security: introduce file caps
Date: Thu, 23 Nov 2006 15:41:59 -0600 [thread overview]
Message-ID: <20061123214159.GA23800@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20061123103920.8d908952.akpm@osdl.org>
Quoting Andrew Morton (akpm@osdl.org):
> On Thu, 23 Nov 2006 13:12:03 +0100
> Chris Friedhoff <chris@friedhoff.org> wrote:
>
> > xinit respects capabilities (at least i guess), so when the system has
> > capability-support, the binary /usr/X11R6/bin/xinit neeeds the
> > capability cap_kill even when no capability extended attribute exists
> > for this binary.
> >
> > setfcaps cap_kill=ep /usr/X11R6/bin/xinit
> >
> > I documented this here:
> > http://www.friedhoff.org/fscaps.html#Xorg,%20xinit,%20xfce,%20kde
> >
> > and for more:
> > http://www.friedhoff.org/fscaps.html
> >
>
> Even when CONFIG_SECURITY_FS_CAPABILITIES=n?
No, the patch shouldn't change behavior when
CONFIG_SECURITY_FS_CAPABILITIES=n, though of course I see why it did. I
will send a fixed patch tomorrow or this weekend.
sorry,
-serge
next prev parent reply other threads:[~2006-11-23 21:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 3:06 security: introduce file caps Serge E. Hallyn
2006-11-15 8:55 ` Chris Friedhoff
2006-11-23 8:14 ` Andrew Morton
2006-11-23 8:22 ` Andrew Morton
[not found] ` <20061123131203.f7b6972f.chris@friedhoff.org>
2006-11-23 18:39 ` Andrew Morton
2006-11-23 21:41 ` Serge E. Hallyn [this message]
2006-11-23 23:21 ` Chris Friedhoff
2006-11-24 16:16 ` file caps: permit unsafe signaling when CONFIG_FS_CAPS=n Serge E. Hallyn
2006-11-24 18:17 ` Serge E. Hallyn
2006-11-25 21:19 ` Chris Friedhoff
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=20061123214159.GA23800@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=chris@friedhoff.org \
--cc=chrisw@sous-sol.org \
--cc=jmorris@namei.org \
--cc=kaigai@kaigai.gr.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
/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