xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: xen-devel@lists.xen.org
Subject: Re: Possible to prevent dom0 accessing guest memory?
Date: Mon, 14 Nov 2016 20:35:01 +0000	[thread overview]
Message-ID: <20161114203501.GP1804@bitfolk.com> (raw)
In-Reply-To: <CAFLBxZY-pBVGYYTUxnyerf3kjh09UZuUG5C3uhbbTZRxk5Cajg@mail.gmail.com>

Hi George,

On Mon, Nov 14, 2016 at 05:09:01PM +0000, George Dunlap wrote:
> There is probably a way to configure Xen to make it possible to build
> domains while making a full dump-core difficult to implement even by a
> motivated attacker; but that would be quite a bit more work (and very
> bespoke to your own particular situation).

I think if it could be made extremely difficult for a compromised
dom0 to dump guest memory then that would be useful to a wide range
of Xen users, as compromise of general purpose Linux hosts (like
most people's dom0s) is pretty commonplace.

Though I was reminded off-list (thanks for that), that Intel SGX and
AMD SME include features which can protect guest memory from other
guests/host/dom0, so perhaps that is a more sensible direction to go
in.

Thanks,
Andy

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2016-11-14 20:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 14:51 Possible to prevent dom0 accessing guest memory? Andy Smith
2016-11-14 15:06 ` Andrew Cooper
2016-11-14 15:29   ` Andy Smith
2016-11-14 17:09     ` George Dunlap
2016-11-14 20:35       ` Andy Smith [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=20161114203501.GP1804@bitfolk.com \
    --to=andy@strugglers.net \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).