From: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
To: Chris Wright <chrisw@osdl.org>
Cc: Alexander Nyberg <alexn@dsv.su.se>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
rmk+lkml@arm.linux.org.uk
Subject: Re: Capabilities across execve
Date: Sat, 19 Mar 2005 01:02:43 +0100 [thread overview]
Message-ID: <873busijto.fsf@goat.bogus.local> (raw)
In-Reply-To: <20050315235851.GF5389@shell0.pdx.osdl.net> (Chris Wright's message of "Tue, 15 Mar 2005 15:58:51 -0800")
Chris Wright <chrisw@osdl.org> writes:
> * Alexander Nyberg (alexn@dsv.su.se) wrote:
>> I can see useful scenarios of having the possiblity of capabilities per
>> inode (it appears the xattr way wins somewhat in the previous
>> discussion).
>
> It's how it should be done.
I agree to disagree :-)
>> Chris, have you seen any capabilities+xattr patches around?
>
> http://www.kernel.org/pub/linux/libs/security/linux-privs/kernel-2.4-fcap/
Which is pretty useless, since it doesn't apply to any recent
(> 2.4.3) kernel. If you insist on a xattr based approach, take
Andy Lutomirski's <http://www.stanford.edu/~luto/linux-fscap/>
patch. It is more recent, a lot smaller and considerably more
understandable (at least for me ;-).
Regards, Olaf.
next prev parent reply other threads:[~2005-03-19 0:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 11:42 Capabilities across execve Alexander Nyberg
2005-03-13 3:21 ` Chris Wright
2005-03-15 14:46 ` Alexander Nyberg
2005-03-15 21:57 ` Russell King
2005-03-15 22:42 ` Chris Wright
2005-03-15 23:41 ` Alexander Nyberg
2005-03-15 23:58 ` Chris Wright
2005-03-16 0:34 ` Alexander Nyberg
2005-03-19 0:02 ` Olaf Dietsche [this message]
2005-03-13 18:32 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2005-03-16 0:04 Albert Cahalan
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=873busijto.fsf@goat.bogus.local \
--to=olaf+list.linux-kernel@olafdietsche.de \
--cc=akpm@osdl.org \
--cc=alexn@dsv.su.se \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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.