xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Jose A. Lopes" <jabolopes@google.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Paul Durrant <Paul.Durrant@citrix.com>
Subject: Re: Guest to Host communication
Date: Thu, 31 Oct 2013 20:02:29 +0000	[thread overview]
Message-ID: <1383249749.5436.112.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <CAN3zuTWOxZjGhHpOeec4tEKUgi=5r5xOCyhBvSu5FHvqdOQHsw@mail.gmail.com>

On Thu, 2013-10-31 at 19:42 +0100, Jose A. Lopes wrote:

> When you say "look inside" the filesystem do you mean to mount that
> filesystem
> in the host OS? If so, it seems that it is very dangerous to mount
> guest filesystems
> due to a number of exploits.

If you only need r/o access from the host then you could use
tools/libfsimage (which has python binding, used by pygrub) which at
least constrains things to a userspace process and not a kernel mode
exploit. With suitable privilege dropping this can be made reasonably
safe...

Ian.

  reply	other threads:[~2013-10-31 20:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22  7:59 Guest to Host communication Jose A. Lopes
2013-10-22  8:48 ` Paul Durrant
2013-10-22 12:48   ` Jose A. Lopes
2013-10-22 13:18     ` Paul Durrant
2013-10-22 13:42       ` Jose A. Lopes
2013-10-31 14:21         ` George Dunlap
2013-10-31 16:08           ` Jose A. Lopes
2013-10-31 16:13             ` George Dunlap
2013-10-31 18:42               ` Jose A. Lopes
2013-10-31 20:02                 ` Ian Campbell [this message]
2013-11-04 10:51                   ` Jose A. Lopes
2013-10-22 13:54       ` Konrad Rzeszutek Wilk

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=1383249749.5436.112.camel@dagon.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=jabolopes@google.com \
    --cc=xen-devel@lists.xenproject.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).