From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: dax@gurulabs.com (Dax Kelson)
Cc: chris@scary.beasts.org (chris@scary.beasts.org),
linux-kernel@vger.kernel.org (linux-kernel@vger.kernel.org),
torvalds@transmeta.com (Linus Torvalds),
alan@lxorguk.ukuu.org.uk (Alan Cox),
marcelo@conectiva.com.br (marcelo@conectiva.com.br)
Subject: Re: [PATCH] Completely honor prctl(PR_SET_KEEPCAPS, 1)
Date: Wed, 8 May 2002 21:17:39 +0100 (BST) [thread overview]
Message-ID: <E175XsZ-0002IO-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.44.0205081341160.10496-100000@mooru.gurulabs.com> from "Dax Kelson" at May 08, 2002 01:55:51 PM
> prtctl(PR_SET_KEEPCAPS, 1)
> setuid(uid)
> setgid(gid)
>
> The end result is exactly the same. I'm trying to envision how this patch
> would change security in a negative way. I keep coming back to the Unix
> idea of "don't be smarter than the admin; don't try to protect root from
> himself".
>
> Maybe we could enchance PR_SET_KEEPCAPS so that:
>
> prtctl(PR_SET_KEEPCAPS, 2) kept both the permitted and the effective caps.
If thats the concern (and its a fair one) then just fix 2.5 not 2.4. 2.4
stuff will need to do the usermode fixes anyway due to old releases
next prev parent reply other threads:[~2002-05-08 19:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 7:27 [PATCH] lockfree rtcache lookup using RCU Dipankar Sarma
2002-05-08 8:10 ` David S. Miller
2002-05-08 8:54 ` Dipankar Sarma
2002-05-08 9:09 ` David S. Miller
2002-05-08 13:24 ` Dipankar Sarma
2002-05-08 13:45 ` David S. Miller
2002-05-14 11:42 ` Dipankar Sarma
2002-05-08 9:40 ` [PATCH] Completely honor prctl(PR_SET_KEEPCAPS, 1) Dax Kelson
2002-05-08 13:42 ` Keith Owens
2002-05-08 19:28 ` chris
2002-05-08 19:38 ` chris
2002-05-08 19:55 ` Dax Kelson
2002-05-08 20:17 ` Alan Cox [this message]
2002-05-08 21:20 ` chris
2002-05-08 21:29 ` Dax Kelson
2002-05-08 20:21 ` [RFC] Making capabilites useful with legacy apps Dax Kelson
2002-05-13 12:55 ` Pavel Machek
2002-05-13 20:28 ` Neil Schemenauer
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=E175XsZ-0002IO-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=chris@scary.beasts.org \
--cc=dax@gurulabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.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®