All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Russell Coker <russell@coker.com.au>,
	Casey Schaufler <casey@schaufler-ca.com>,
	libvir-list@redhat.com, selinux@tycho.nsa.gov
Subject: Re: [ANNOUNCE][RFC] sVirt: Integrating SELinux and Linux-based virtualization
Date: Wed, 13 Aug 2008 12:21:44 -0400	[thread overview]
Message-ID: <200808131221.44201.paul.moore@hp.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0808121906120.13656@tundra.namei.org>

On Tuesday 12 August 2008 5:57:19 am James Morris wrote:
> On Tue, 12 Aug 2008, Russell Coker wrote:
> > One thing that should be noted is the labelled network benefits. 
> > If you had several groups of virtual servers running at different
> > levels and wanted to prevent information leaks then having SE Linux
> > contexts and labelled networking could make things a little easier.
> >
> > I have had some real challenges in managing firewall rules for Xen
> > servers. My general practice is to try and make sure that there is
> > no real need for firewalls between hosts on the same hardware (not
> > that I want it this way - it's what technical and management issues
> > force me to).
> >
> > So for example if I have an ISP Xen server running virtual machines
> > for a number of organisations I make sure that they are either all
> > within a similar trust boundary (IE affiliated groups) or all
> > mutually untrusting (IE other IP addresses in the same net-block
> > are treated the same as random hosts on the net).
>
> Thanks for the insights -- we expect to address the virtual
> networking aspect in some way.

I think we could do some pretty cool things here with the new, well 
2.6.25 new, network ingress/egress controls and restricting VM 
instances to specific interfaces and/or networks.  However, we would 
need to settle the basic VM label management issues first.

-- 
paul moore
linux @ hp

--
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.

  reply	other threads:[~2008-08-13 16:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11  2:17 [ANNOUNCE][RFC] sVirt: Integrating SELinux and Linux-based virtualization James Morris
2008-08-11  4:41 ` Casey Schaufler
2008-08-11  9:31   ` James Morris
2008-08-12  4:15     ` Casey Schaufler
2008-08-12  5:57     ` Russell Coker
2008-08-12  9:57       ` James Morris
2008-08-13 16:21         ` Paul Moore [this message]
     [not found] ` <20080812110803.GI13067@redhat.com>
2008-08-12 11:25   ` [libvirt] " James Morris
2008-08-12 13:20     ` Daniel J Walsh
     [not found]       ` <20080812132513.GN13067@redhat.com>
2008-08-12 13:54         ` Daniel J Walsh
     [not found]           ` <20080812140620.GO13067@redhat.com>
2008-08-12 14:16             ` Daniel J Walsh
2008-08-15  8:02 ` [ANNOUNCE][RFC] sVirt: Integrating SELinux and Linux-basedvirtualization Atsushi SAKAI
2008-08-15  9:07   ` James Morris

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=200808131221.44201.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=casey@schaufler-ca.com \
    --cc=jmorris@namei.org \
    --cc=libvir-list@redhat.com \
    --cc=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    /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.