From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: liutgnu@yahoo.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] A question about postcopy safety
Date: Mon, 5 Sep 2016 15:00:09 +0100 [thread overview]
Message-ID: <20160905140009.GE24656@redhat.com> (raw)
In-Reply-To: <20160905135214.GA22496@work-vm>
On Mon, Sep 05, 2016 at 02:52:14PM +0100, Dr. David Alan Gilbert wrote:
> * liutgnu@yahoo.com (liutgnu@yahoo.com) wrote:
> > Hi David,
>
> Hi Liutao,
>
> > I'm studying the process of postcopy migration, and I found that the memory pages migrated from source to destination are not encrypted. Does this make the VM vulnerable if it's memory has been tampered with during postcopy migration?
> >
> > I think precopy has less risk because the source's memory is always altering. If one page is tampered with during network transfer, with source still running, then a later version of that page may keep updating. So it would be quite difficult to track all different page versions, and tamper with the final version of one page.
> >
> > But when it comes to postcopy, the situation is riskier because one specific page is only transferred once. It's easy to capture all transferring memory pages, tamper and resend.
>
> I don't think there's much difference between precopy and postcopy for security;
> the only secure way to do migration is over an encrypted transport and that solves
> it for both precopy and postcopy.
Agreed, there's no real world difference in the security of pre & post copy.
If you care about security there's no avoiding the need to use an encrypted
transport.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2016-09-05 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <110743700.1285610.1472475080274.ref@mail.yahoo.com>
2016-08-29 12:51 ` [Qemu-devel] A question about postcopy safety liutgnu
2016-08-29 14:00 ` Kashyap Chamarthy
2016-09-05 13:52 ` Dr. David Alan Gilbert
2016-09-05 14:00 ` Daniel P. Berrange [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=20160905140009.GE24656@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=liutgnu@yahoo.com \
--cc=qemu-devel@nongnu.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 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.