From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] General question: Encrypytion on virtual servers (VPS/Vserver)
Date: Tue, 21 Feb 2017 17:21:24 +0100 [thread overview]
Message-ID: <20170221162124.GA22918@tansi.org> (raw)
In-Reply-To: <20170221135807.GI17041@redhat.com>
On Tue, Feb 21, 2017 at 14:58:07 CET, Daniel P. Berrange wrote:
> On Tue, Feb 21, 2017 at 02:42:51PM +0100, michaelof@rocketmail.com wrote:
[...]
> If the attacker has access to the physical host while your VM is running,
> then (with current hardware) there is essentially nothing you can do to
> prevent a skilled person getting your master key out of VM memory. AMD
> recently announced a memory encryption feature that might make it possible
> to protect guest keys from a host attacker, but its still very early days
> in its developement & integration into virtualization technology, so a very
> long way off being available in any public hosting provider.
I think this is more about proteching VMs from each other than
from the Hypervisor, think memory deduplication, copy-on-write
and caches that leak information from one VM to another.
Regards,
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2017-02-21 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 13:42 [dm-crypt] General question: Encrypytion on virtual servers (VPS/Vserver) michaelof
2017-02-21 13:58 ` Daniel P. Berrange
2017-02-21 16:21 ` Arno Wagner [this message]
2017-02-21 16:33 ` Daniel P. Berrange
2017-02-21 18:14 ` Arno Wagner
2017-02-21 13:59 ` Arno Wagner
2017-02-21 14:13 ` Michael Kjörling
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=20170221162124.GA22918@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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