From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Jan Kundr?t <jan.kundrat@fzu.cz>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
Mark Williamson <maw48@hermes.cam.ac.uk>,
xen-devel@lists.sourceforge.net
Subject: Re: protecting xen startup
Date: Wed, 24 Nov 2004 00:21:37 +0000 [thread overview]
Message-ID: <20041124002137.GJ5146@lkcl.net> (raw)
In-Reply-To: <41A3B319.6090401@fzu.cz>
On Tue, Nov 23, 2004 at 11:00:57PM +0100, Jan Kundr?t wrote:
> Luke Kenneth Casson Leighton wrote:
> >
> > perhaps i should explain: i am looking to use xen to implement
> > a new level of paranoid security.
> >
> > i aim to run single applications, such as firefox and
> > openoffice, in their own dedicated virtual machines, a
> > localised file server in one (or more if i can get GFS or OCFS2
> > to work) virtual machine(s), and for the applications to each
> > connect to the xen master running an x-server [nomachine isn't
> > quite suitable, i may have to write my own ssh-based x-proxy].
>
> Do you mean running xserver in domain0?
um, yes.
> You should better setup separate
> domain for it.
really? is that possible?
can i run an xserver in a separate guest OS and still allow the guest
OS direct access to the screen?
how is that done - via a framebuffer drive?
tellmetellme!!!!
> But are you sure that such a setup will be usable and fast enough?
i gonna find out :)
> > allowing a compromised guest OS to fire up another virtual
> > machine, connect to the x-server and spoof "please enter your
> > password" dialog boxes is therefore to be avoided!!!
>
> If I'm not mistaken, you can start up new VMs only from domain0 or
> through HTTP interface, So you can easily firewall all traffic inside
> domain0 to local port 8000 (except for 127.0.0.1/32).
yeh, *grumble*, and you can also, in selinux, ban applications from
accessing a port.
> j.
>
--
--
<a href="http://lkcl.net">http://lkcl.net</a>
--
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-11-24 0:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 17:05 protecting xen startup Luke Kenneth Casson Leighton
2004-11-23 18:07 ` Mike Wray
2004-11-23 21:03 ` Luke Kenneth Casson Leighton
2004-11-23 18:07 ` Mark Williamson
2004-11-23 20:51 ` Luke Kenneth Casson Leighton
2004-11-23 21:03 ` Ian Pratt
2004-11-23 21:52 ` Luke Kenneth Casson Leighton
2004-11-23 22:00 ` Jan Kundrát
2004-11-24 0:21 ` Luke Kenneth Casson Leighton [this message]
2004-11-24 8:17 ` Mark Williamson
2004-11-24 10:39 ` Luke Kenneth Casson Leighton
2004-11-23 22:49 ` Mark Williamson
2004-11-24 0:18 ` [Xen-devel] " Luke Kenneth Casson Leighton
2004-11-24 0:18 ` Luke Kenneth Casson Leighton
2004-11-24 8:27 ` Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 17:33 Charles Coffing
2004-11-23 17:58 ` Mike Wray
2004-11-23 23:58 Neugebauer, Rolf
2004-11-24 10:53 ` Luke Kenneth Casson Leighton
2004-11-24 11:55 ` Mark Williamson
2004-11-24 11:48 Neugebauer, Rolf
2004-11-24 15:24 ` Luke Kenneth Casson Leighton
2004-11-24 20:24 ` Luke Kenneth Casson Leighton
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=20041124002137.GJ5146@lkcl.net \
--to=lkcl@lkcl.net \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=jan.kundrat@fzu.cz \
--cc=maw48@hermes.cam.ac.uk \
--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.