From: Jan Kara <jack@suse.cz>
To: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.23: Filesystem capabilities 0.17
Date: Thu, 1 Nov 2007 22:54:24 +0100 [thread overview]
Message-ID: <20071101215424.GA27788@duck.suse.cz> (raw)
In-Reply-To: <87tzo5925v.fsf@olafdietsche.de>
On Thu 01-11-07 20:49:32, Olaf Dietsche wrote:
> Jan Kara <jack@suse.cz> writes:
>
> >> This patch implements filesystem capabilities. It allows to
> >> run privileged executables without the need for suid root.
> > Hmm, is there some "design document" so that one does not have to poke
> > through the code and find out what it's actually trying to do?
>
> What do you mean with "trying to do"? I thought this is obvious, it
> provides executables with filesystem capabilities.
Well, yes, that was obvious but I rather meant "how is it doing it?".
So where does it store these bits and such.
> > Also why don't you use extended attributes or store them inside the
> > executable like Pavel did (you link it from your web page).
>
> The links from my web page are there to show alternatives, nothing
> else. When I started in 2002, xattr where pretty new or nonexistant.
OK, I see. I'm not sure it's going to make it when we already have an
implementation of the functionality in kernel as Serge mentioned.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2007-11-01 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 16:08 [PATCH] 2.6.23: Filesystem capabilities 0.17 Olaf Dietsche
2007-10-31 17:08 ` Jan Kara
2007-11-01 19:49 ` Olaf Dietsche
2007-11-01 21:54 ` Jan Kara [this message]
2007-11-01 22:22 ` Olaf Dietsche
2007-11-02 4:21 ` Casey Schaufler
2007-11-02 9:07 ` Olaf Dietsche
2007-11-05 11:09 ` Jan Kara
2007-11-07 14:42 ` Olaf Dietsche
2007-10-31 17:36 ` Serge E. Hallyn
2007-11-01 19:54 ` 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=20071101215424.GA27788@duck.suse.cz \
--to=jack@suse.cz \
--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