mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: "Laughlin, Joseph V" <Joseph.V.Laughlin@boeing.com>
Cc: Steve Youngs <steve@youngs.au.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Modifying kernel so that non-root users have some root capabilities
Date: Mon, 24 May 2004 16:49:56 -0700	[thread overview]
Message-ID: <20040524164956.P22989@build.pdx.osdl.net> (raw)
In-Reply-To: <67B3A7DA6591BE439001F2736233351202B47E87@xch-nw-28.nw.nos.boeing.com>; from Joseph.V.Laughlin@boeing.com on Mon, May 24, 2004 at 04:41:59PM -0700

* Laughlin, Joseph V (Joseph.V.Laughlin@boeing.com) wrote:
> > From: Steve Youngs [mailto:steve@youngs.au.com] 
> > 
> > I'm assuming that there are user-land tools to do these 
> > things now for root, right?  So why not look into things like 
> > sudo(8) or even setuid executables? 
> 
> In short, it comes down to permissions problems with NFS mounted
> directories, combined with Rational ClearCase issues, combined with
> stringent security requirements.

Uh-oh, sounds like an insurmountable problem ;-) Well, keep in mind that
CAP_SYS_NICE and CAP_IPC_LOCK can DoS a machine pretty nicely.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2004-05-24 23:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24 23:41 Laughlin, Joseph V
2004-05-24 23:49 ` Chris Wright [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-25 23:43 Roger Larsson
2004-05-25 19:06 Laughlin, Joseph V
2004-05-25 21:15 ` Bill Davidsen
     [not found] <fa.nbdv424.kmij3i@ifi.uio.no>
2004-05-24 23:43 ` Andy Lutomirski
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

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=20040524164956.P22989@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=Joseph.V.Laughlin@boeing.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve@youngs.au.com \
    /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®