All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Lee <nic-lists@plumtree.co.nz>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Adam Heath <doogie@brainfood.com>,
	"xen-devel@lists.sourceforge.net"
	<xen-devel@lists.sourceforge.net>,
	Bastian Blank <waldi@debian.org>
Subject: Re: severe security issue on dom0/xend/xm/non-root	users
Date: Sat, 5 Mar 2005 12:19:54 +1300	[thread overview]
Message-ID: <20050304231954.GC18627@stateless> (raw)
In-Reply-To: <1109966042.3351.15.camel@localhost>

On Fri, Mar 04, 2005 at 01:54:02PM -0600, Anthony Liguori wrote:
> I'm not saying it's a non-issue :-)  It's one of the reasons I'm working
> on VM-Tools.  Security is not something you can just retro-fit into
> something.  It has to be designed in from the beginning.

How stable is VM-Tools for a purely single computer Xen system? No
migration features. Just startup and shutdown of domUs. ie. As a
replacement for UML.


> That said, I don't think Xend not being secure on a hostile dom0 is a
> bug per-say.  Really, having a hostile dom0 is putting an awful lot of
> faith in the Linux syscall interface.

If someone has privileged access to block devices, then there really
isn't much you can do.

However, doesn't mean that you can't work hard to make it difficult to
abuse. Security after all is a layer approach. The more you do at each
level, the less options an attacker has.

However, delegating all network security to iptables is a bad idea IMO.
Leaves you open for when iptables breaks.


Is it possible to turn off the migration features of xend completely?
ie. remove the need for the network layer.

Nicholas



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  parent reply	other threads:[~2005-03-04 23:19 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 17:23 severe security issue on dom0/xend/xm/non-root users Adam Heath
2005-03-04 19:01 ` Anthony Liguori
2005-03-04 19:19   ` Rich Persaud
2005-03-04 19:47     ` Anthony Liguori
2005-03-04 19:39       ` Adam Heath
2005-03-04 19:56       ` Bastian Blank
2005-03-05 21:53         ` Rik van Riel
2005-03-05 22:28           ` Bastian Blank
2005-03-06 15:14           ` Tommi Virtanen
2005-03-06 21:14             ` Rik van Riel
2005-03-13 14:55               ` Kurt Garloff
2005-03-13 16:00                 ` Rik van Riel
2005-03-13 17:09                   ` Kurt Garloff
2005-03-13 21:39                 ` David Hopwood
2005-03-13 21:51                   ` Kurt Garloff
2005-03-14 14:58                     ` Philip R Auld
2005-03-14 15:16                       ` Kurt Garloff
2005-03-14 15:54                         ` Philip R Auld
2005-03-14 16:13                           ` Kurt Garloff
2005-03-14 16:44                             ` Anthony Liguori
2005-03-17  6:46                             ` Tommi Virtanen
2005-03-17 15:02                               ` Kurt Garloff
2005-03-18  9:19                                 ` Tommi Virtanen
2005-03-18  9:31                                   ` Kurt Garloff
2005-03-18 11:59                                     ` Tommi Virtanen
2005-03-19 11:21                                       ` Nuutti Kotivuori
2005-03-19  2:33                                   ` David Hopwood
2005-03-19  6:29                                     ` Anthony Liguori
2005-03-05  3:14       ` David Hopwood
2005-03-05  7:54         ` Anthony Liguori
2005-03-04 19:35   ` Adam Heath
2005-03-04 19:54     ` Anthony Liguori
2005-03-04 19:47       ` Rich Persaud
2005-03-04 23:19       ` Nicholas Lee [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-13 17:17 Ian Pratt

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=20050304231954.GC18627@stateless \
    --to=nic-lists@plumtree.co.nz \
    --cc=aliguori@us.ibm.com \
    --cc=doogie@brainfood.com \
    --cc=waldi@debian.org \
    --cc=xen-devel@lists.sourceforge.net \
    /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.