From: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
To: Valdis.Kletnieks@vt.edu
Cc: Chris Wright <chrisw@osdl.org>,
Andy Lutomirski <luto@myrealbox.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] capabilites, take 2
Date: Fri, 14 May 2004 07:33:32 +0200 [thread overview]
Message-ID: <874qqj1sk3.fsf@goat.bogus.local> (raw)
In-Reply-To: <200405140135.i4E1Zp7A025139@turing-police.cc.vt.edu> (Valdis Kletnieks's message of "Thu, 13 May 2004 21:35:51 -0400")
Valdis.Kletnieks@vt.edu writes:
> On Thu, 13 May 2004 18:20:10 PDT, Chris Wright said:
>
>> I think it still needs more work. Default behavoiur is changed, like
>> Inheritble is full rather than clear, setpcap is enabled, etc. Also,
>> why do you change from Posix the way exec() updates capabilities? Sure,
>> there is no filesystem bits present, so this changes the calculation,
>> but I'm not convinced it's as secure this way. At least with newcaps=0.
>
> The last time the "capabilities" thread reared its head a while ago, Andy made
> a posting that pretty conclusively showed that the Posix way was totally b0rken
> if you ever intended to support filesystem bits. So if you wanted to ever have
> a snowball's chance of supporting something like:
>
> chcap cap_net_raw+ep /bin/ping
Seems like you're not aware of:
<http://www.olafdietsche.de/linux/capability/>
This supports filesystem capabilities with the current (POSIX?)
implementation. So, whatever Andy has shown, it has at least one
counter evidence q.e.d.
> 2) Toss all the filesystems capabilities support out the window.
I agree to disagree ;-)
Regards, Olaf.
next prev parent reply other threads:[~2004-05-14 5:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 20:08 Andy Lutomirski
2004-05-14 1:20 ` Chris Wright
2004-05-14 1:35 ` Valdis.Kletnieks
2004-05-14 4:51 ` Chris Wright
2004-05-14 5:33 ` Olaf Dietsche [this message]
2004-05-14 6:04 ` Valdis.Kletnieks
2004-05-14 7:09 ` Olaf Dietsche
2004-05-14 2:27 ` Andy Lutomirski
2004-05-14 4:48 ` Chris Wright
2004-05-14 5:58 ` Andy Lutomirski
2004-05-14 17:45 ` Chris Wright
2004-05-14 6:39 ` Olaf Dietsche
2004-05-14 2:45 ` [PATCH] capabilities, take 3 (Re: [PATCH] capabilites, take 2) Andy Lutomirski
2004-05-14 5:04 ` Chris Wright
2004-05-14 5:32 ` Valdis.Kletnieks
2004-05-14 5:40 ` Chris Wright
2004-05-14 6:25 ` Valdis.Kletnieks
2004-05-14 11:10 ` Olaf Dietsche
2004-05-14 14:15 ` Andy Lutomirski
2004-05-15 15:50 ` Olaf Dietsche
2004-05-14 12:03 [PATCH] capabilites, take 2 Albert Cahalan
2004-05-14 14:53 ` Andy Lutomirski
2004-05-14 17:58 ` Chris Wright
2004-05-14 15:21 ` Stephen Smalley
2004-05-14 15:19 ` Albert Cahalan
2004-05-14 18:06 ` Stephen Smalley
2004-05-14 17:32 ` Albert Cahalan
2004-05-14 21:11 ` Chris Wright
2004-05-14 19:32 ` Albert Cahalan
2004-05-14 18:00 ` Chris Wright
2004-05-14 17:48 ` Chris Wright
[not found] <fa.dt4cg55.jnqvr5@ifi.uio.no>
[not found] ` <fa.mu5rj3d.24gtbp@ifi.uio.no>
2004-05-14 15:57 ` Andy Lutomirski
2004-05-14 16:01 ` Stephen Smalley
2004-05-14 16:18 ` Andy Lutomirski
2004-05-14 16:37 ` Stephen Smalley
2004-05-14 18:07 ` Chris Wright
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=874qqj1sk3.fsf@goat.bogus.local \
--to=olaf+list.linux-kernel@olafdietsche.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@myrealbox.com \
/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®