On Thu, Jun 27, 2013 at 08:05:38AM -0400, Hamilton, Peter A. wrote:
> > It also means you can't change the password of an existing image - you have
> > to create a new image with a new password & re-encrypt the data.
>
> Following up on this point, since "qemu-img create" cannot be used to specif
e conducted up to this point seem to indicate that this is true.
Thanks,
Peter
-Original Message-
From: Daniel P. Berrange [mailto:berra...@redhat.com]
Sent: Thursday, June 27, 2013 5:36 AM
To: Hamilton, Peter A.
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-img create encrypt
On Wed, Jun 26, 2013 at 02:52:51PM -0400, Hamilton, Peter A. wrote:
> I've been doing some work with qemu-img and encrypted qcow2 images and have
> noticed that "qemu-img create" does not prompt for a password to encrypt new
> images, defaulting (from the documentation I've read) to the empty strin
"Hamilton, Peter A." writes:
> I've been doing some work with qemu-img and encrypted qcow2 images and have
> noticed that "qemu-img create" does not prompt for a password to encrypt new
> images, defaulting (from the documentation I've read) to the empty string as
> a password. Why does "qemu-img
I've been doing some work with qemu-img and encrypted qcow2 images and have
noticed that "qemu-img create" does not prompt for a password to encrypt new
images, defaulting (from the documentation I've read) to the empty string as
a password. Why does "qemu-img create" work this way?
I haven't been
