public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Shiva V <shivaramakrishnan740@gmail.com>, kvm@vger.kernel.org
Subject: Re: Integrity in untrusted environments
Date: Fri, 01 Aug 2014 08:50:30 +0200	[thread overview]
Message-ID: <53DB38B6.1080405@redhat.com> (raw)
In-Reply-To: <loom.20140731T230604-167@post.gmane.org>

Il 31/07/2014 23:25, Shiva V ha scritto:
> Hello,
>  I am exploring ideas to implement a service inside a virtual machine on 
> untrusted hypervisors under current cloud infrastructures.
>  Particularly, I am interested how one can verify the integrity of the 
> service in an environment where hypervisor is not trusted. This is my setup.
> 
> 1. I have two virtual machines. (Normal client VM's).
> 2. VM-A is executing a service and VM-B wants to verify its integrity.
> 3. Both are executing on untrusted hypervisor.
> 
> Though, Intel SGX will solve this, by using the concept of enclaves, its not 
> publicly available yet.
> 
> One could also use SMM to verify the integrity. But since this is time based 
> approach, one could easily exploit between the time window.
> 
> I was drilling down this idea, We know Write xor Execute Memory Protection 
> Scheme. Using this idea,If we could lock down the VM-A memory pages where 
> the service is running and also corresponding page-table entries, then have 
> a handler code that temporarily unlocks them for legitimate updates, then 
> one could verify the integrity of the service running. 

You can make a malicious hypervisor that makes all executable pages also
writable, but hides the fact to the running process.  But really, if you
control the hypervisor you can just write to guest memory as you wish.

SMM will be emulated by the hypervisor.

If the hypervisor is untrusted, you cannot solve _everything_.  For the
third time, what attacks are you trying to protect from?

Paolo

  parent reply	other threads:[~2014-08-01  6:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 21:25 Integrity in untrusted environments Shiva V
2014-07-31 21:40 ` Nakajima, Jun
2014-07-31 22:19   ` Shiva V
2014-08-01  6:50 ` Paolo Bonzini [this message]
2014-08-01 15:43   ` Shiva V

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=53DB38B6.1080405@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=shivaramakrishnan740@gmail.com \
    /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