From: "Benoît Canet" <benoit.canet@irqsave.net>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] QCOW2 cryptography and secure key handling
Date: Tue, 23 Jul 2013 15:21:04 +0200 [thread overview]
Message-ID: <20130723132104.GC5002@irqsave.net> (raw)
In-Reply-To: <20130723130053.GW2477@redhat.com>
> > Do you (the block maintainers) have an idea on how the code could be improved
> > to securely pass the crypto key to the QCOW2 code ?
>
> More generally, QCow2's current encryption support is woefully inadequate
> from a design POV. If we wanted better encryption built-in to QEMU it is
> best to just deprecate the current encryption support and define a new
> qcow2 extension based around something like the LUKS data format. Using
> the LUKS data format precisely would be good from a data portability
> POV, since then you can easily switch your images between LUKS encrypted
> block device & qcow2-with-luks image file, without needing to re-encrypt
> the data.
Thanks I will read the LUKS specification.
Best regards
Benoît
next prev parent reply other threads:[~2013-07-23 13:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 12:47 [Qemu-devel] QCOW2 cryptography and secure key handling Benoît Canet
2013-07-23 13:00 ` Daniel P. Berrange
2013-07-23 13:21 ` Benoît Canet [this message]
2013-07-23 14:40 ` Benoît Canet
2013-07-23 15:22 ` Stefan Hajnoczi
2013-07-23 15:38 ` Kevin Wolf
2013-07-23 15:57 ` Daniel P. Berrange
2013-07-24 13:07 ` Benoît Canet
2013-07-24 15:30 ` Paolo Bonzini
2013-07-24 15:33 ` Daniel P. Berrange
2013-07-24 15:40 ` Paolo Bonzini
2013-07-24 15:46 ` Daniel P. Berrange
2013-07-29 11:21 ` Markus Armbruster
2013-07-29 11:25 ` Kevin Wolf
2013-07-29 11:32 ` Daniel P. Berrange
2013-07-29 16:07 ` Benoît Canet
2013-07-31 15:33 ` Benoît Canet
2013-07-31 15:27 ` Benoît Canet
2013-07-31 17:52 ` Laszlo Ersek
2013-07-31 18:31 ` Laszlo Ersek
2013-07-23 15:40 ` 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=20130723132104.GC5002@irqsave.net \
--to=benoit.canet@irqsave.net \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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.