From: Andy Lutomirski <luto@stanford.edu>
To: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.0-test6: Filesystem capabilities 0.15
Date: Sat, 04 Oct 2003 00:18:18 -0700 [thread overview]
Message-ID: <3F7E743A.9010601@stanford.edu> (raw)
In-Reply-To: <fa.ign8c9e.3g8vr4@ifi.uio.no>
Olaf Dietsche wrote:
> This *untested* patch implements filesystem capabilities. It allows
> to run privileged executables without the need for suid root.
>
> Changes: - updated to 2.6.0-test6 - added lscap to show fs caps for a
> particular file
>
> This patch is available at:
> <http://www.olafdietsche.de/linux/capability/>
>
I have an alternate patch, implementing file capabilities using xattrs.
It also implements the
exec changes I proposed a few days back, but this time around it's a
config option. Note that
this patch is very non-intrusive. The user API is through setxattr and
friends, and the changes
to any filesystem to support this patch are minimal (add the
system.capabilities xattr and
validate its contents on setxattr).
The patch and user tools are at http://www.stanford.edu/~luto/linux-fscap/
(Apply the cap- patches in order. Patches are against 2.6.0-test6 vanilla.)
Olaf -- what do you think? (I like your CAP_SETFCAP addition -- I may
add it to my patch.
Currently anyone can chcap their own files, as long as they hold the
capabilities they want
to permit.)
Example:
$ su
# cp `which ping` myping
# chmod 755 myping
# chcap cap_net_raw+p myping
# exit
$ ./myping localhost
-- Andy Lutomirski
next parent reply other threads:[~2003-10-04 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ign8c9e.3g8vr4@ifi.uio.no>
2003-10-04 7:18 ` Andy Lutomirski [this message]
2003-10-04 22:45 ` Olaf Dietsche
2003-10-03 23:55 Olaf Dietsche
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=3F7E743A.9010601@stanford.edu \
--to=luto@stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf+list.linux-kernel@olafdietsche.de \
/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®