On 2/6/19 1:55 PM, Max Reitz wrote: > Currently, you can give no encryption format for a qcow2 file while > still passing a key-secret. That does not conform to the schema, so > this patch changes the schema to allow it. > > Signed-off-by: Max Reitz <[email protected]> > --- > qapi/block-core.json | 31 ++++++++++++++++++++++++++++--- > block/qcow2.c | 3 +++ > 2 files changed, 31 insertions(+), 3 deletions(-) >
> @@ -2961,10 +2964,30 @@ > # @BlockdevQcow2EncryptionFormat: > # @aes: AES-CBC with plain64 initialization venctors We should fix that typo. > # > +# @auto: Determine the encryption format from the image > +# header. This only allows the use of the > +# key-secret option. (Since: 4.0) > +# > # Since: 2.10 Reviewed-by: Eric Blake <[email protected]> -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
