From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] new setprocuid syscall
Date: Tue, 20 Feb 2001 14:19:01 MET-1 [thread overview]
Message-ID: <1605A1153EC8@vcnet.vc.cvut.cz> (raw)
On 20 Feb 01 at 7:11, Peter Samuelson wrote:
> [Alan Cox]
> > There is an assumption in the kernel that only the task changes its
> > own uid and other related data.
>
> Fair enough but could you explain the potential problems? And how is
> it different from sys_setpriority?
Look at what fs/open.c:sys_access does, at least. It switches
fsuid/fsgid/capabilities during its execution.
sys_setpriority is completely different, no piece of kernel changes that
and nothing except schedule() touches that. But {,fs,e}[ug]id are used
here and there through whole kernel. Also, changing priority does not
remove some access rights from your process, while changing uid/gid does...
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2001-02-20 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 14:19 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-23 17:13 [PATCH] new setprocuid syscall Bernd Jendrissek
2001-02-19 22:18 BERECZ Szabolcs
2001-02-20 5:01 ` Peter Samuelson
2001-02-20 10:53 ` Martin Dalecki
2001-02-20 13:00 ` Peter Samuelson
2001-02-20 11:42 ` Alan Cox
2001-02-20 13:11 ` Peter Samuelson
2001-02-20 13:52 ` Alan Cox
2001-02-20 17:04 ` BERECZ Szabolcs
2000-01-01 0:28 ` Pavel Machek
2001-02-21 4:19 ` Peter Samuelson
2001-02-20 12:14 ` BERECZ Szabolcs
2001-02-20 12:52 ` Peter Samuelson
2001-02-20 12:02 ` Philipp Rumpf
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=1605A1153EC8@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@cadcamlab.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 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.