qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>, Alberto Garcia <berto@igalia.com>
Subject: Re: [Qemu-devel] [PATCH v8 12/20] qcow2: extend specification to cover LUKS encryption
Date: Thu, 1 Jun 2017 13:04:30 -0500	[thread overview]
Message-ID: <d0a2d5b5-0279-8c05-69da-4ed3d928618f@redhat.com> (raw)
In-Reply-To: <20170601172734.9039-13-berrange@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]

On 06/01/2017 12:27 PM, Daniel P. Berrange wrote:
> Update the qcow2 specification to describe how the LUKS header is
> placed inside a qcow2 file, when using LUKS encryption for the
> qcow2 payload instead of the legacy AES-CBC encryption
> 
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Reviewed-by: Alberto Garcia <berto@igalia.com>
> Reviewed-by: Max Reitz <mreitz@redhat.com>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
>  docs/specs/qcow2.txt | 103 +++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 103 insertions(+)
> 

> +== Data encryption ==
> +
> +When an encryption method is requested in the header, the image payload
> +data must be encrypted/decrypted on every write/read. The image headers
> +and metadata are never encrypted.
> +
> +The algorithms used for encryption vary depending on the method
> +
> + - AES:
> +
> +   The AES cipher, in CBC mode, with 256 bit keys.
> +
> +   Initialization vectors generated using plain64 method, with
> +   the virtual disk sector as the input tweak.
> +
> +   This format is no longer supported in QEMU system emulators, due
> +   to a number of design flaws affecting it security. It is only

s/affecting it/affecting its/

Can keep my R-b.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2017-06-01 18:04 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
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 [this message]
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=d0a2d5b5-0279-8c05-69da-4ed3d928618f@redhat.com \
    --to=eblake@redhat.com \
    --cc=berrange@redhat.com \
    --cc=berto@igalia.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 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).