From: Andreas Gruenbacher <agruen@suse.de>
To: Olaf Dietsche <olaf.dietsche#list.linux-kernel@t-online.de>
Cc: linux-kernel@vger.kernel.org,
Chris Evans <chris@scary.beasts.org>,
Ulrich Drepper <drepper@redhat.com>,
Pavel Machek <pavel@atrey.karlin.mff.cuni.cz>
Subject: Re: [PATCH][RFC] 2.5.44 (1/2): Filesystem capabilities kernel patch
Date: Tue, 29 Oct 2002 12:35:51 +0100 [thread overview]
Message-ID: <200210291235.51299.agruen@suse.de> (raw)
In-Reply-To: <87n0oxmrhn.fsf@goat.bogus.local>
On Tuesday 29 October 2002 12:09, Olaf Dietsche wrote:
> Andreas Gruenbacher <agruen@suse.de> writes:
> > A perhaps unrelated note: We once had Pavel Machek's elfcap
> > implementation, in which capabilities were stored in ELF. This was a bad
> > idea because being able to create executables does not imply the user is
> > capable of CAP_SETFCAP, and users shouldn't be able to freely choose
> > their capabilities :-] We still want
>
> I remember this hack and since I hear this claim every now and then, I
> downloaded his patch and verified with the source. Pavel's capability
> patch was about _restricting_ not granting capabilities, so it's more
> like an inheritable, rather than a permitted, set.
>
> At least that was his intention. I didn't verify this with the
> appropriate kernel sources from 1999.
I forgot to CC Pavel the last time. Elfcap probably truly was restrictive
only. This is comparable to dropping capabilities very early in the suid root
binaries themselves, and thus not a significant improvement.
We want to be able to also grant capabilities (not only restrict them), so we
may have fewer suid root binaries.
--Andreas.
next prev parent reply other threads:[~2002-10-29 11:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 19:07 [PATCH][RFC] 2.5.42 (1/2): Filesystem capabilities kernel patch Olaf Dietsche
2002-10-18 23:00 ` Alexander Viro
2002-10-19 0:07 ` Olaf Dietsche
2002-10-19 0:25 ` Alexander Viro
2002-10-24 12:25 ` [PATCH][RFC] 2.5.44 " Olaf Dietsche
2002-10-28 22:56 ` Olaf Dietsche
2002-10-28 23:36 ` chris
2002-10-29 0:20 ` Olaf Dietsche
2002-10-29 1:08 ` Olaf Dietsche
2002-10-29 11:08 ` Olaf Dietsche
2002-10-29 11:18 ` Chris Evans
2002-10-29 2:23 ` Andreas Gruenbacher
2002-10-29 11:09 ` Olaf Dietsche
2002-10-29 11:35 ` Andreas Gruenbacher [this message]
2002-10-29 12:04 ` __libc_enable_secure check (was: [PATCH][RFC] 2.5.44 (1/2): Filesystem capabilities kernel patch) Olaf Dietsche
2002-10-29 14:38 ` [PATCH][RFC] 2.5.44 (1/2): Filesystem capabilities kernel patch Olaf Dietsche
2002-10-20 0:24 ` [PATCH][RFC] 2.5.42 " Andreas Gruenbacher
2002-10-21 15:25 ` Olaf Dietsche
2002-10-21 22:03 ` Andreas Gruenbacher
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=200210291235.51299.agruen@suse.de \
--to=agruen@suse.de \
--cc=chris@scary.beasts.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf.dietsche#list.linux-kernel@t-online.de \
--cc=pavel@atrey.karlin.mff.cuni.cz \
/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