From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Colin Walters <walters@verbum.org>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: xen 2.0 - adding selinux permissions
Date: Thu, 25 Nov 2004 09:22:43 +0000 [thread overview]
Message-ID: <20041125092242.GA16115@lkcl.net> (raw)
In-Reply-To: <1101345346.1543.7.camel@nexus.verbum.private>
On Wed, Nov 24, 2004 at 08:15:46PM -0500, Colin Walters wrote:
> On Wed, 2004-11-24 at 20:19 +0000, Luke Kenneth Casson Leighton wrote:
> > On Wed, Nov 24, 2004 at 01:13:15PM -0500, Colin Walters wrote:
> > > On Wed, 2004-11-24 at 15:49 +0000, Luke Kenneth Casson Leighton wrote:
> > >
> > > > okay, regarding the second argument to avc_has_perm(),
> > > > i asked the nice xen developers if it'd be possible to
> > > > associate a sid with each virtual machine.
> > >
> > > When would you want a process to be able to control one Xen machine but
> > > not another?
> >
> > i described such a scenario in an earlier message today to stephen:
> > giving an operator-admin the right to reboot a VM running a SQL server
> > but NOT giving that same operator the right to reboot the master OS
> > which, if you rebooted that, would take down every single VM with it.
>
> The most flexible approach would be to make the management daemon a
> userspace object manager,
it's already userspace.
> like dbus and nscd. Give it a config file
> (like the dbus <associate>) which maps VMs to security contexts. Then
> label the /proc/xen interface specifically, and ensure that only the
> daemon can interact with it.
ah. good idea.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2004-11-25 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 22:03 xen 2.0 - adding selinux permissions Luke Kenneth Casson Leighton
2004-11-24 13:39 ` Stephen Smalley
2004-11-24 15:09 ` Luke Kenneth Casson Leighton
2004-11-24 15:06 ` Stephen Smalley
2004-11-24 15:49 ` Luke Kenneth Casson Leighton
2004-11-24 15:54 ` Stephen Smalley
2004-11-24 17:10 ` Luke Kenneth Casson Leighton
2004-11-24 18:13 ` Colin Walters
2004-11-24 20:19 ` Luke Kenneth Casson Leighton
2004-11-25 1:15 ` Colin Walters
2004-11-25 9:22 ` Luke Kenneth Casson Leighton [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=20041125092242.GA16115@lkcl.net \
--to=lkcl@lkcl.net \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@tycho.nsa.gov \
--cc=walters@verbum.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.