From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:32779) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W5zey-0001QR-WA for qemu-devel@nongnu.org; Wed, 22 Jan 2014 10:24:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W5zeu-0002dP-3S for qemu-devel@nongnu.org; Wed, 22 Jan 2014 10:24:08 -0500 Received: from mx1.redhat.com ([209.132.183.28]:15817) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W5zet-0002d1-QM for qemu-devel@nongnu.org; Wed, 22 Jan 2014 10:24:04 -0500 Message-ID: <52DFE290.5080401@redhat.com> Date: Wed, 22 Jan 2014 08:24:00 -0700 From: Eric Blake MIME-Version: 1.0 References: <1390393704-16067-1-git-send-email-berrange@redhat.com> In-Reply-To: <1390393704-16067-1-git-send-email-berrange@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0bxt1PQ67e1qft6uSQB4meCrShucM0KWJ" Subject: Re: [Qemu-devel] [PATCH v2] Describe flaws in qcow/qcow2 encryption in the docs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" , qemu-devel@nongnu.org Cc: Kevin Wolf , Paolo Bonzini , Stefan Hajnoczi , Peter Maydell This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --0bxt1PQ67e1qft6uSQB4meCrShucM0KWJ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 01/22/2014 05:28 AM, Daniel P. Berrange wrote: >=20 > Recommend against any use of QCow/QCow2 encryption, directing > users to dm-crypt / LUKS which can meet modern cryptography > best practices. >=20 > Signed-off-by: Daniel P. Berrange > --- > qemu-doc.texi | 23 ++++++++++++++++++++--- > qemu-img.texi | 23 ++++++++++++++++++++--- > 2 files changed, 40 insertions(+), 6 deletions(-) > + > +@itemize @minus > +@item The AES-CBC cipher is used with predictable initialization vecto= rs based > +on the sector number. This makes it vulnerable to chosen plaintext att= acks > +which can reveal the existence of encrypted data. > +@item The user passphrase is directly used as the encryption key. A po= orly > +choosen or short passphrase will compromise the security of the encryp= tion. s/choosen/chosen/ (both files) > +In the event of the passphrase being compromised there is no way to ch= ange and still my question whether this deserves a third @item. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --0bxt1PQ67e1qft6uSQB4meCrShucM0KWJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJS3+KQAAoJEKeha0olJ0NqMugIAKjjyddP/EYqV5uTACCGWswV X+kEHcq2vzy4Xg/4oKzkYg/vbzbCwcMeO0ON0s+VjigjXAT4Ii/Y9NHuLKVlb0cq GG3OeEtySsviO42GnPn/apxls5LqCMIHFcJEqCwJ3PUIBtYd1XL4I/SJoLxxGmO/ NbfXeVsCE8Nm/IcJfC/daY2xZrezjzRStRKkyIoJbZ9G6O2kG3UGZkgT9TAIQWTA efrfH8DChOeYy0CvN5CWjNsPbe8zY/cTFH89xBktn4RMSt/oLYXemdwjF4ce7nfX M6dCLtx2YaL+FUQLhpbymhCy9rQjFpi22BcW7yMUHNWLBymNmEdoQSe9LexRO3E= =NgSr -----END PGP SIGNATURE----- --0bxt1PQ67e1qft6uSQB4meCrShucM0KWJ--