From: Enrico Weigelt <weigelt@metux.de>
To: linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: API for changing UIDs of other processes
Date: Mon, 5 May 2008 15:20:30 +0200 [thread overview]
Message-ID: <20080505132030.GE32019@nibiru.local> (raw)
In-Reply-To: <alpine.LNX.1.10.0805021602160.6463@fbirervta.pbzchgretzou.qr>
* Jan Engelhardt <jengelh@medozas.de> wrote:
> >Now I'd like to add an write capability to these files:
> >simply writing another number changes the (|s|fs)uid.
> >
> >But this doesnt seem that trivial. Perhaps someone could give
> >me some advice ?
>
> Not really hard, is it? Just look at something like oom_adj
Well, it's not that trivial than just an ro string file.
But not that hard as I first suspected :)
I've introduced a few new helpers for rw integers, which works
quite similar to the ro string stuff, but with anouther handler type.
I'll post a patch in the new testers list.
The next step is actually changing the uid. Can I just write
new values to the uid field(s) in the task struct or is there
something tricky about that ?
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
prev parent reply other threads:[~2008-05-05 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 12:16 API for changing UIDs of other processes Enrico Weigelt
2008-05-02 14:07 ` Jan Engelhardt
2008-05-05 13:20 ` Enrico Weigelt [this message]
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=20080505132030.GE32019@nibiru.local \
--to=weigelt@metux.de \
--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