From: Chris Friedhoff <chris@friedhoff.org>
To: "Serge E. Hallyn" <sergeh@us.ibm.com>
Cc: "chris@friedhoff.org" <chris@friedhoff.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Posix file capabilities in 2.6.24rc2
Date: Wed, 14 Nov 2007 10:12:51 +0100 [thread overview]
Message-ID: <20071114101251.a1f6214d.chris@friedhoff.org> (raw)
In-Reply-To: <20071113235318.GA6477@sergelap.austin.ibm.com>
Hello Serge,
I wanted only to express what I observed.
A "yes it should" confirms its ok.
And yes, I haven't looked into the patches and the name and commentary
of file-capabilities-clear-fcaps-on-inode-change.patch explains this
already.
I'm preparing to update my page http://www.friedhoff.org/fscaps.html
for 2.6.24, and I also want to explain what one has to take into account
or be beware off. If I stumble about this, I think others will also
(imho).
I have written a script to change suid binaries and servers,
automating the examples I give on the webpage.
In the sequence of commands I was setting fscaps and than chown the
binary. Now with the aforementioned patch the fscaps are removed when
I chown and the script wasn't working anymore. My point is not my
script, it's being surprised and being a bit at a loss. Documenting
this helps to clarify things and users to adopt this feature.
The matter with "xinit: Operation not permitted..." happens, when I
(unprivileged user) close a from a console started X session. Similar to
Andrew Morton'S http://lkml.org/lkml/2006/11/23/15 . The 2.6.24-rc2
kernel has capabilties enabled but /usr/bin/xinit has no capabilities
set. It remains the black screen with a cursor, the windowmanager is
closed. Is this known? Is this a problem? Does anyone else observes
this?
As far as I understand, I dont have to grant / to use capabilities even
when the kernel has capabilities enabled.
Chris
On Tue, 13 Nov 2007 17:53:18 -0600
"Serge E. Hallyn" <sergeh@us.ibm.com> wrote:
> Quoting Chris Friedhoff (chris@friedhoff.org):
> > Hello,
> >
> > everything works as expected, but ...
> >
> > closing X and no capabilities set for xinit does shutdown only the
> > windowmanager and not the X server (Xorg server 1.4)
> > Consolemessage is:
> > xinit: Operation not permitted (errno 1): Can't kill X server
> >
> >
> > the xattr capability is removed, when the file is chown'ed.
>
> Hi Chris,
>
> yes on chown the capability is removed. I'm not quite sure what
> you're asking? Is your setup depending on being able to chown
> while keeping file capabilities? Can you give some more details?
>
> thanks,
> -serge
--------------------
Chris Friedhoff
chris@friedhoff.org
next prev parent reply other threads:[~2007-11-14 9:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 22:07 Posix file capabilities in 2.6.24rc2 Chris Friedhoff
2007-11-13 23:53 ` Serge E. Hallyn
2007-11-14 9:12 ` Chris Friedhoff [this message]
2007-11-14 18:02 ` Serge E. Hallyn
2007-11-15 22:02 ` Chris Friedhoff
2007-11-19 13:39 ` Posix file capabilities in 2.6.24rc2; now 2.6.24-rc3 Chris Friedhoff
2007-11-19 23:16 ` Serge E. Hallyn
2007-11-20 9:46 ` Chris Friedhoff
2007-11-20 14:51 ` Serge E. Hallyn
2007-11-20 22:29 ` Chris Friedhoff
2007-11-20 22:51 ` Serge E. Hallyn
2007-11-21 0:50 ` Chris Friedhoff
2007-11-22 7:42 ` Andrew Morgan
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=20071114101251.a1f6214d.chris@friedhoff.org \
--to=chris@friedhoff.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergeh@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.