From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Joerg Roedel <joro@8bytes.org>
Cc: Daniel Schwager <Daniel.Schwager@dtnet.de>, kvm@vger.kernel.org
Subject: Re: How to secret Dom0 against DomU .
Date: Fri, 20 Feb 2009 19:20:27 +0100 [thread overview]
Message-ID: <499EF46B.4050008@wpkg.org> (raw)
In-Reply-To: <20090220165016.GJ2125@8bytes.org>
Joerg Roedel schrieb:
> On Fri, Feb 20, 2009 at 05:26:22PM +0100, Daniel Schwager wrote:
>> Hi,
>>
>> are there some known issues using kvm-84
>> - to break in into the Dom0
>> - to corrupt the Dom0
>> - to ... Dom0
>>
>> Are there some thinks I have to configure in Dom0
>> to safe Dom0 against DomU's ?
>
> This is absolutly no risk in KVM just because there is no Dom0. I guess
> you mean if there is any way to break out of a guest and hack the host.
> As far as I know there are no known security issue.
He may also want to prevent guest from accessing the host via network.
Place the guest in a different VLAN, attach to a different bridge etc.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2009-02-20 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 16:26 How to secret Dom0 against DomU Daniel Schwager
2009-02-20 16:50 ` Joerg Roedel
2009-02-20 18:20 ` Tomasz Chmielewski [this message]
2009-02-20 18:25 ` Daniel Schwager
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=499EF46B.4050008@wpkg.org \
--to=mangoo@wpkg.org \
--cc=Daniel.Schwager@dtnet.de \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox