All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] keys in memory?
Date: Thu, 13 Jan 2011 22:31:01 +0100	[thread overview]
Message-ID: <4D2F6F15.6000209@redhat.com> (raw)
In-Reply-To: <375AD447-08EA-41C6-8366-C62CAE8CE5DF@nytimes.com>

On 01/13/2011 10:03 PM, Kachler, Arie wrote:
> When a system has been configured and it's using encrypted LUKS
> partition(s), are they keys visible in memory?

for active devices yes. if you run encryption on the main CPU
(and not in some special hw), the key must be visible in memory.

> The question is relevant when deploying these types of partitions to
> a cloud provider, where the provider's hypervisor has access to all
> vms' memory.

if you have access to hypervisor, you have access to the full memory,
you have access to everything.

Milan

  reply	other threads:[~2011-01-13 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 21:03 [dm-crypt] keys in memory? Kachler, Arie
2011-01-13 21:31 ` Milan Broz [this message]
2011-01-13 23:56 ` Arno Wagner
2011-01-14  8:53   ` Milan Broz
2011-01-14 15:25     ` Kachler, Arie

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=4D2F6F15.6000209@redhat.com \
    --to=mbroz@redhat.com \
    --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 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.