From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36593) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WJl9n-0001qk-9z for qemu-devel@nongnu.org; Sat, 01 Mar 2014 09:44:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WJl9b-0007mD-Lo for qemu-devel@nongnu.org; Sat, 01 Mar 2014 09:44:51 -0500 Received: from mail-qc0-x230.google.com ([2607:f8b0:400d:c01::230]:61647) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WJl9b-0007m6-Gd for qemu-devel@nongnu.org; Sat, 01 Mar 2014 09:44:39 -0500 Received: by mail-qc0-f176.google.com with SMTP id m20so1757249qcx.21 for ; Sat, 01 Mar 2014 06:44:38 -0800 (PST) Sender: Paolo Bonzini Message-ID: <5311F251.1030904@redhat.com> Date: Sat, 01 Mar 2014 15:44:33 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <87wqgflzno.fsf@blackfin.pond.sub.org> <531108CA.1060002@redhat.com> In-Reply-To: <531108CA.1060002@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] The unholy encrypted image key mess List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake , Markus Armbruster , qemu-devel@nongnu.org Cc: Kevin Wolf , Gerd Hoffmann , Stefan Hajnoczi Il 28/02/2014 23:08, Eric Blake ha scritto: > Use the fact that we are calling the next release "2.0" to actually kill > qemu disk encryption as a horribly botched feature, on the grounds that > we are doing users a favor by not letting them use broken encryption? Only for qemu, of course---qemu-img would still have support for encryption, and there's no reason to risk stability by removing all the monitor code right now. However, wouldn't we have the same problems even with a sane encrypted image format (based on LUKS, for example)? Let's just open bugs (oh if only Launchpad supported tracker bugs) for now. Paolo