From: "Bill O'Donnell" <billodo@sgi.com>
To: KaiGai Kohei <kaigai@kaigai.gr.jp>,
"Serge E. Hallyn" <serue@us.ibm.com>,
Chris Friedhoff <chris@friedhoff.org>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [PATCH] Implement file posix capabilities
Date: Wed, 24 Jan 2007 10:30:05 -0600 [thread overview]
Message-ID: <20070124163004.GA15979@sgi.com> (raw)
In-Reply-To: <4570F373.5090608@kaigai.gr.jp>
I'm in the process of testing the (backported) capabilities patch
and Kaigai's userspace tools on a SLES10 based x86-64 target (2.6.16).
Chris Friedhoff's examples (http://www.friedhoff.org/fscaps.html)
run cleanly. That said, can one expect, through the use of these
enhanced capabilities, to be able to add some finer grain
capabilities based on a specific userid? In Chris' ping example,
the suid is removed from /bin/ping to restrict it to root, and a
capability added to allow any user to execute it. Can that example
be extended to make it so only a _particular_ user can execute it?
I realize with SELinux, one could achieve the goal, but as a stopgap,
can capabilities be used to get there?
Thanks,
Bill
--
Bill O'Donnell
SGI
billodo@sgi.com
next prev parent reply other threads:[~2007-01-24 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 17:07 [PATCH] Implement file posix capabilities Serge E. Hallyn
2006-11-29 10:28 ` Chris Friedhoff
2006-11-29 20:40 ` Bill O'Donnell
2006-11-30 18:05 ` Bill O'Donnell
2006-11-30 22:57 ` Serge E. Hallyn
2006-12-01 19:28 ` Bill O'Donnell
2006-12-02 3:30 ` KaiGai Kohei
2007-01-24 16:30 ` Bill O'Donnell [this message]
2007-01-24 20:24 ` Casey Schaufler
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=20070124163004.GA15979@sgi.com \
--to=billodo@sgi.com \
--cc=chris@friedhoff.org \
--cc=kaigai@kaigai.gr.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=serue@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.