From: "Daniel P. Berrange" <berrange@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Eric Blake <eblake@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Alberto Garcia <berto@igalia.com>
Subject: Re: [Qemu-devel] [PATCH v8 07/20] block: deprecate "encryption=on" in favor of "encrypt.format=aes"
Date: Mon, 19 Jun 2017 14:56:14 +0100 [thread overview]
Message-ID: <20170619135614.GE2640@redhat.com> (raw)
In-Reply-To: <bcff6607-5095-4b98-54ca-b65ecbac0474@redhat.com>
On Wed, Jun 07, 2017 at 06:40:32PM +0200, Max Reitz wrote:
> On 2017-06-01 19:27, Daniel P. Berrange wrote:
> > Historically the qcow & qcow2 image formats supported a property
> > "encryption=on" to enable their built-in AES encryption. We'll
> > soon be supporting LUKS for qcow2, so need a more general purpose
> > way to enable encryption, with a choice of formats.
> >
> > This introduces an "encrypt.format" option, which will later be
> > joined by a number of other "encrypt.XXX" options. The use of
> > a "encrypt." prefix instead of "encrypt-" is done to facilitate
> > mapping to a nested QAPI schema at later date.
> >
> > e.g. the preferred syntax is now
> >
> > qemu-img create -f qcow2 -o encrypt.format=aes demo.qcow2
> >
> > Reviewed-by: Eric Blake <eblake@redhat.com>
> > Reviewed-by: Alberto Garcia <berto@igalia.com>
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > ---
> > block/qcow.c | 30 ++++++++++++++---
> > block/qcow2.c | 33 +++++++++++++++----
> > include/block/block_int.h | 2 +-
> > qemu-img.c | 4 ++-
> > tests/qemu-iotests/082.out | 81 ++++++++++++++++++++++++++++++----------------
> > 5 files changed, 110 insertions(+), 40 deletions(-)
> >
> > diff --git a/block/qcow.c b/block/qcow.c
> > index 6738bc7..42f83b2 100644
> > --- a/block/qcow.c
> > +++ b/block/qcow.c
>
> [...]
>
> > @@ -818,8 +818,16 @@ static int qcow_create(const char *filename, QemuOpts *opts, Error **errp)
> > }
> >
> > backing_file = qemu_opt_get_del(opts, BLOCK_OPT_BACKING_FILE);
> > - if (qemu_opt_get_bool_del(opts, BLOCK_OPT_ENCRYPT, false)) {
> > - flags |= BLOCK_FLAG_ENCRYPT;
> > + encryptfmt = qemu_opt_get_del(opts, BLOCK_OPT_ENCRYPT_FORMAT);
> > + if (encryptfmt) {
> > + if (qemu_opt_get_bool_del(opts, BLOCK_OPT_ENCRYPT, false)) {
>
> You should probably just use qemu_opt_get_del(opts, BLOCK_OPT_ENCRYPT)
> here, because otherwise you can do this:
>
> $ ./qemu-img create -f qcow -o encryption=off,encrypt.format=aes \
> foo.qcow 64M
> Formatting 'foo.qcow', fmt=qcow size=67108864 encryption=off
> encrypt.format=aes
Yes, will fix it as you suggest.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-06-19 13:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 17:27 [Qemu-devel] [PATCH v8 00/20] Convert QCow[2] to QCryptoBlock & add LUKS support Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 01/20] block: expose crypto option names / defs to other drivers Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 02/20] block: add ability to set a prefix for opt names Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 03/20] qcow: document another weakness of qcow AES encryption Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 04/20] qcow: require image size to be > 1 for new images Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 05/20] iotests: skip 042 with qcow which dosn't support zero sized images Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 06/20] iotests: skip 048 with qcow which doesn't support resize Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 07/20] block: deprecate "encryption=on" in favor of "encrypt.format=aes" Daniel P. Berrange
2017-06-07 16:40 ` Max Reitz
2017-06-19 13:56 ` Daniel P. Berrange [this message]
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 08/20] qcow: make encrypt_sectors encrypt in place Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 09/20] qcow: convert QCow to use QCryptoBlock for encryption Daniel P. Berrange
2017-06-07 16:55 ` Max Reitz
2017-06-19 13:58 ` Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 10/20] qcow2: make qcow2_encrypt_sectors encrypt in place Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 11/20] qcow2: convert QCow2 to use QCryptoBlock for encryption Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 12/20] qcow2: extend specification to cover LUKS encryption Daniel P. Berrange
2017-06-01 18:04 ` Eric Blake
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 13/20] qcow2: add support for LUKS encryption format Daniel P. Berrange
2017-06-07 17:19 ` Max Reitz
2017-06-19 14:00 ` Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 14/20] qcow2: add iotests to cover LUKS encryption support Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 15/20] iotests: enable tests 134 and 158 to work with qcow (v1) Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 16/20] block: rip out all traces of password prompting Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 17/20] block: remove all encryption handling APIs Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 18/20] block: pass option prefix down to crypto layer Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 19/20] qcow2: report encryption specific image information Daniel P. Berrange
2017-06-01 18:08 ` Eric Blake
2017-06-02 8:32 ` Alberto Garcia
2017-06-07 17:38 ` Max Reitz
2017-06-19 14:08 ` Daniel P. Berrange
2017-06-01 17:27 ` [Qemu-devel] [PATCH v8 20/20] docs: document encryption options for qcow, qcow2 and luks Daniel P. Berrange
2017-06-07 17:44 ` [Qemu-devel] [PATCH v8 00/20] Convert QCow[2] to QCryptoBlock & add LUKS support Max Reitz
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=20170619135614.GE2640@redhat.com \
--to=berrange@redhat.com \
--cc=berto@igalia.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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.