From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48313) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1by0-0003Nu-C4 for qemu-devel@nongnu.org; Tue, 23 Jul 2013 08:45:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V1bxw-00011v-GG for qemu-devel@nongnu.org; Tue, 23 Jul 2013 08:45:24 -0400 Received: from nodalink.pck.nerim.net ([62.212.105.220]:47442 helo=paradis.irqsave.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1bxw-000114-6U for qemu-devel@nongnu.org; Tue, 23 Jul 2013 08:45:20 -0400 Date: Tue, 23 Jul 2013 14:47:06 +0200 From: =?iso-8859-1?Q?Beno=EEt?= Canet Message-ID: <20130723124706.GB5002@irqsave.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] QCOW2 cryptography and secure key handling List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: kwolf@redhat.com, stefanha@redhat.com Hi, I have some budget to improve QCOW2's cryptography. My main concern is that the QCOW2 image crypto key is passed in clear tex= t. Do you (the block maintainers) have an idea on how the code could be impr= oved to securely pass the crypto key to the QCOW2 code ? Best regards Beno=EEt