From: Stanislav Brabec <utx@penguin.cz>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <k.kooi@student.utwente.nl>
Subject: Re: Requiring root access for windowmanagers?
Date: Sat, 29 Nov 2008 21:52:47 +0100 [thread overview]
Message-ID: <20081129215247.52c40a2b@zaurus> (raw)
In-Reply-To: <20081129010422.ecd2adb6.raster@rasterman.com>
Sat, 29 Nov 2008 01:04:22 +1100
Carsten Haitzler (The Rasterman) wrote:
> On Fri, 28 Nov 2008 13:20:12 +0100 Koen Kooi
> <k.kooi@student.utwente.nl> babbled:
> > What's the consensus on requiring root access for running an OE
> > built windowmanager?
> >
> > Case in point: e-wm does 'renice -10', which only root is allow to
> > do.
> >
> > Proposal: remove the 'renice' so regular users can start a window
> > manager as well.
>
> i did this specifically for performance. basically it makes things
> MUCH smoother.
I understand your trick - I do the same with video player if I want to
compile in parallel with DVD playback.
Running WM as root would increase any security hole to root access flaw.
I can see cleaner solutions:
1. Write a small SUID wrapper. Change priority, drop permissions, run
window manager.
2. Run WM as root and drop privileges after setting priority.
3. Use capabilities and enable CAP_SYS_NICE.
4. And finally, the best solution may be a different kernel scheduler.
But I don't follow the development there, so I don't know, whether
there is possible to find a good solution: "This process does not eat a
much CPU time, but it wants fast processing".
--
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus
next prev parent reply other threads:[~2008-11-29 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 12:20 Requiring root access for windowmanagers? Koen Kooi
2008-11-28 13:26 ` Koen Kooi
2008-11-28 14:04 ` Carsten Haitzler
2008-11-29 20:52 ` Stanislav Brabec [this message]
2008-11-29 21:39 ` Carsten Haitzler
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=20081129215247.52c40a2b@zaurus \
--to=utx@penguin.cz \
--cc=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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