From: David T Hollis <dhollis@davehollis.com>
To: "Laughlin, Joseph V" <Joseph.V.Laughlin@boeing.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modifying kernel so that non-root users have some root capabilities
Date: Tue, 25 May 2004 10:57:38 -0400 [thread overview]
Message-ID: <1085497058.3270.4.camel@dhollis-lnx.kpmg.com> (raw)
In-Reply-To: <67B3A7DA6591BE439001F2736233351202B47E6F@xch-nw-28.nw.nos.boeing.com>
On Mon, 2004-05-24 at 15:21 -0700, Laughlin, Joseph V wrote:
> (not sure if this is a duplicate or not.. Apologies in advance.)
>
> I've been tasked with modifying a 2.4 kernel so that a non-root user can
> do the following:
>
> Dynamically change the priorities of processes (up and down)
> Lock processes in memory
> Can change process cpu affinity
>
> Anyone got any ideas about how I could start doing this? (I'm new to
> kernel development, btw.)
>
> Thanks,
>
It's these sorts of things that make Windows so unstable. As others
have suggested, the considerably safer alternatives have already
surfaced, been around, had the tires kicked etc. in the form of setuid,
sudo, or kernel capabilities. Some of these things may even be possible
from SELinux, but I'm not certain.
--
David T Hollis <dhollis@davehollis.com>
next prev parent reply other threads:[~2004-05-25 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 22:21 Laughlin, Joseph V
2004-05-24 23:24 ` Steve Youngs
2004-05-24 23:29 ` Neale Banks
2004-05-25 11:28 ` Richard B. Johnson
2004-05-25 18:14 ` Bill Davidsen
2004-05-25 14:57 ` David T Hollis [this message]
2004-05-24 23:41 Laughlin, Joseph V
2004-05-24 23:49 ` Chris Wright
[not found] <fa.nbdv424.kmij3i@ifi.uio.no>
2004-05-24 23:43 ` Andy Lutomirski
2004-05-25 19:06 Laughlin, Joseph V
2004-05-25 21:15 ` Bill Davidsen
2004-05-25 23:43 Roger Larsson
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=1085497058.3270.4.camel@dhollis-lnx.kpmg.com \
--to=dhollis@davehollis.com \
--cc=Joseph.V.Laughlin@boeing.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
all inboxes | Powered by JetHome®