From: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.23: Filesystem capabilities 0.17
Date: Thu, 01 Nov 2007 23:22:51 +0100 [thread overview]
Message-ID: <87fxzp8v2c.fsf@olafdietsche.de> (raw)
In-Reply-To: <20071101215424.GA27788@duck.suse.cz> (Jan Kara's message of "Thu\, 1 Nov 2007 22\:54\:24 +0100")
Jan Kara <jack@suse.cz> writes:
> 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.
The bits are stored in a sparse file named /.capabilities in the
directory of the mount point, where the corresponding executable
lives. The inode number of the file is the index into this file.
Regards, Olaf.
next prev parent reply other threads:[~2007-11-01 22:23 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
2007-11-01 22:22 ` Olaf Dietsche [this message]
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=87fxzp8v2c.fsf@olafdietsche.de \
--to=olaf+list.linux-kernel@olafdietsche.de \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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.