[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <520194.24968.qm@web36605.mail.mud.yahoo.com>
Date: Thu, 1 Nov 2007 21:21:56 -0700 (PDT)
From: Casey Schaufler <casey@...aufler-ca.com>
To: Olaf Dietsche <olaf+list.linux-kernel@...fdietsche.de>,
Jan Kara <jack@...e.cz>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] 2.6.23: Filesystem capabilities 0.17
--- Olaf Dietsche <olaf+list.linux-kernel@...fdietsche.de> wrote:
> Jan Kara <jack@...e.cz> writes:
>
> > On Thu 01-11-07 20:49:32, Olaf Dietsche wrote:
> >> Jan Kara <jack@...e.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.
The old PlanG approach. It's the way that we did MAC labels in
Trix4. It has the wicked advantage of working across NFS without
anyone being the wiser. It really causes trouble for backup
utilities, however. Trix6 (there wasn't really a Trix5) had xattrs
available and we found the switch well worth the investment.
Casey Schaufler
casey@...aufler-ca.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists