From: Chris Wright <chrisw@osdl.org>
To: Steven Dake <sdake@mvista.com>
Cc: Chris Wright <chrisw@osdl.org>, Mark Haverkamp <markh@osdl.org>,
Openais List <openais@lists.osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9 kernel oops with openais
Date: Fri, 29 Oct 2004 17:19:35 -0700 [thread overview]
Message-ID: <20041029171935.X2357@build.pdx.osdl.net> (raw)
In-Reply-To: <1099095114.1207.16.camel@persist.az.mvista.com>; from sdake@mvista.com on Fri, Oct 29, 2004 at 05:11:54PM -0700
* Steven Dake (sdake@mvista.com) wrote:
> What would be preferrable instead of dropping UID when privleged
> services are needed? more specifically I need
> * CAP_NET_RAW (bindtodevice)
> * CAP_SYS_NICE (setscheduler)
> * CAP_IPC_LOCK (mlockall)
You could drop all but those specific capabilities. But, since you only
seem to need those during startup there's not a huge value in doing
anything other than what you're already doing.
> I had thought about adding the correct code to get these capabilities
> but it still requires a start-from-uid0 environment
Dropping uid is a fine idea, esp. since you have to start from uid 0
to get the bind/setsched/mlock bits done. It just exposes a case where
the mlock change might surprise users, which is why I hope it's not the
common usage pattern (and I think most are root apps, so we should be ok).
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-10-30 0:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 22:51 Steven Dake
2004-10-29 23:08 ` Mark Haverkamp
2004-10-29 23:16 ` Steven Dake
2004-10-29 23:39 ` Chris Wright
2004-10-29 23:44 ` Steven Dake
2004-10-29 23:45 ` Chris Wright
2004-10-29 23:57 ` Steven Dake
2004-10-30 0:01 ` Chris Wright
2004-10-30 0:11 ` Steven Dake
2004-10-30 0:19 ` Chris Wright [this message]
2004-10-30 0:42 ` Lee Revell
2004-10-29 23:42 ` Steven Dake
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=20041029171935.X2357@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@osdl.org \
--cc=openais@lists.osdl.org \
--cc=sdake@mvista.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®