From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Benoît Canet" <benoit@irqsave.net>,
"Hamilton, Peter A." <Peter.Hamilton@jhuapl.edu>,
"Markus Armbruster" <armbru@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Coffman, Joel M." <Joel.Coffman@jhuapl.edu>
Subject: Re: [Qemu-devel] Adding dmcrypt to QEMU block drivers
Date: Thu, 20 Mar 2014 09:23:14 +0100 [thread overview]
Message-ID: <20140320082314.GD28673@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20140318133044.GF29054@redhat.com>
On Tue, Mar 18, 2014 at 01:30:44PM +0000, Daniel P. Berrange wrote:
> On Tue, Mar 18, 2014 at 02:08:19PM +0100, Stefan Hajnoczi wrote:
> > On Mon, Mar 17, 2014 at 08:48:08PM -0400, Hamilton, Peter A. wrote:
> > I guess the filter would be deployed below the image format:
> > qcow2 -> luks -> file
>
> I could see it being either above or below the image format at
> mgmt app's choice. Having it above the image format means only
> the payload is encrypted, so you can still query the basic
> metadata (like logic disk size, backing files) without decrypting,
> which is a nice aspect of the way qcow2 encryption historically
> worked. I could see though that people might want even the header
> encrypted to prevent anyone seeing anything about the image format
> without keys.
The difference is that if you encrypt just the payload then dmcrypt
compatibility is much less useful since the data is now intermingled
with image format metadata.
But I agree in some cases it may be the right thing to do.
next prev parent reply other threads:[~2014-03-20 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 0:48 [Qemu-devel] Adding dmcrypt to QEMU block drivers Hamilton, Peter A.
2014-03-18 10:19 ` Markus Armbruster
2014-03-18 13:08 ` Stefan Hajnoczi
2014-03-18 13:30 ` Daniel P. Berrange
2014-03-18 14:09 ` Kevin Wolf
2014-03-20 8:23 ` Stefan Hajnoczi [this message]
2014-03-20 12:41 ` Daniel P. Berrange
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=20140320082314.GD28673@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=Joel.Coffman@jhuapl.edu \
--cc=Peter.Hamilton@jhuapl.edu \
--cc=armbru@redhat.com \
--cc=benoit@irqsave.net \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.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.