From: Keith Owens <kaos@ocs.com.au>
To: Dax Kelson <dax@gurulabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Completely honor prctl(PR_SET_KEEPCAPS, 1)
Date: Wed, 08 May 2002 23:42:29 +1000 [thread overview]
Message-ID: <9176.1020865349@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 08 May 2002 03:40:11 CST." <Pine.LNX.4.44.0205080136560.8607-100000@mooru.gurulabs.com>
On Wed, 8 May 2002 03:40:11 -0600 (MDT),
Dax Kelson <dax@gurulabs.com> wrote:
>Originally when a process set*uided all capabilities bits were cleared.
>Then sometime later (wish BK went back 3 years), the behaviour was
>modified according to the comment "A process may, via prctl(), elect to
>keep its capabilites when it calls setuid() and switches away from
>uid==0. Both permitted and effective sets will be retained."
FWIW, the change was in 2.2.18-pre18, between October 26 and 29, 2000.
I have all the kernel versions from 2.0.21 (1997) through 2.5.14 in a
set of PRCS repositories. A binary chop on 2.2 found the change in a
few minutes.
next prev parent reply other threads:[~2002-05-08 13:42 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 [this message]
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
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=9176.1020865349@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=dax@gurulabs.com \
--cc=linux-kernel@vger.kernel.org \
/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