From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 17C4AC4360C for ; Thu, 26 Sep 2019 13:02:59 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E00BE222BE for ; Thu, 26 Sep 2019 13:02:58 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E00BE222BE Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:35682 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iDTQ9-0004Vy-RJ for qemu-devel@archiver.kernel.org; Thu, 26 Sep 2019 09:02:57 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:46617) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iDTMT-0001yE-LT for qemu-devel@nongnu.org; Thu, 26 Sep 2019 08:59:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iDTMS-0003Rz-Ij for qemu-devel@nongnu.org; Thu, 26 Sep 2019 08:59:09 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51574) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iDTMS-0003Ra-CK for qemu-devel@nongnu.org; Thu, 26 Sep 2019 08:59:08 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 8D06F99BAC; Thu, 26 Sep 2019 12:59:07 +0000 (UTC) Received: from maximlenovopc.usersys.redhat.com (unknown [10.35.206.61]) by smtp.corp.redhat.com (Postfix) with ESMTP id 522D061F2D; Thu, 26 Sep 2019 12:59:06 +0000 (UTC) Message-ID: <67b5d2969705c36cd566f7b7b2381a23c5884dcc.camel@redhat.com> Subject: Re: qcow2 native encryption -- change passphrase? From: Maxim Levitsky To: Craig Mull , qemu-devel@nongnu.org Date: Thu, 26 Sep 2019 15:59:04 +0300 In-Reply-To: References: Content-Type: multipart/alternative; boundary="=-2PGALIh4uPuQCCW9l+ef" Mime-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Thu, 26 Sep 2019 12:59:07 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.132.183.28 X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: John Ferlan , Daniel Berrange Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" --=-2PGALIh4uPuQCCW9l+ef Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2019-09-26 at 12:46 +0000, Craig Mull wrote: > How do you change the passphrase for QCOW2 native encrypted volume? > > > > I've played with qemu-img create and it appears I can only add a passphrase to slot 0 at volume creation time. I don't believe cryptsetup is supported with QCOW2 native encryption to manage LUKS > slots. > > Hi! Currently you can't change the pass-phrase for qcow2 luks encrypted files, but I am working on this exact feature, and it will suport both luks images (as an alternative to cryptosetup, and qcow2 luks images). I expect that soon it will be merged upstream. Best regards, Maxim Levitsky --=-2PGALIh4uPuQCCW9l+ef Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
On Thu, 2019-09-26 at 12:46 +0000, Craig Mull wrote:
Ho= w do you change the passphrase for QCOW2 native encrypted vo= lume?
 
I've played with qemu-img create and it appears I can= only add a passphrase to slot 0 at volume creation time.  I don't bel= ieve cryptsetup is supported with QCOW2 native encryption to manage LUKS sl= ots.
 

Hi!
Currently you can't change the pass-phrase for qcow2 luks encrypted = files, but I am working on this exact feature,
and it will suport= both luks images (as an alternative to cryptosetup, and qcow2 luks images)= .
I expect that soon it will be merged upstream.

Best regards,
Maxim Levitsky
--=-2PGALIh4uPuQCCW9l+ef--