From: Kevin Wolf <kwolf@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: "Benoît Canet" <benoit@irqsave.net>,
"Hamilton, Peter A." <Peter.Hamilton@jhuapl.edu>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Coffman, Joel M." <Joel.Coffman@jhuapl.edu>
Subject: Re: [Qemu-devel] Adding dmcrypt to QEMU block drivers
Date: Tue, 18 Mar 2014 15:09:50 +0100 [thread overview]
Message-ID: <20140318140950.GO4607@noname.str.redhat.com> (raw)
In-Reply-To: <20140318133044.GF29054@redhat.com>
Am 18.03.2014 um 14:30 hat Daniel P. Berrange geschrieben:
> Also, we shouldn't be focusing on QCow2 here. While we're certainly
> aiming to obsolete QCow2's encryption, we should be aiming to cover
> any of the drivers. eg people using the built-in rbd/iscsi/gluster/nfs
> backends want to be able to use encryption too - we don't want to
> force them to abandon the QEMU native block drivers and go to the
> kernel for these network protocols just to use encryption.
I think the part that the qcow2 block driver should be contributing is
just that it can automatically create an encryption layer if the image
file header contains a flag that this new encryption mechanism is used.
This way a similar interface as before could be provided, where the user
basically just says '-hda encrypted.qcow2' and qemu will ask for the
password.
Kevin
next prev parent reply other threads:[~2014-03-18 14:11 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 [this message]
2014-03-20 8:23 ` Stefan Hajnoczi
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=20140318140950.GO4607@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=Joel.Coffman@jhuapl.edu \
--cc=Peter.Hamilton@jhuapl.edu \
--cc=armbru@redhat.com \
--cc=benoit@irqsave.net \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).