| commit | cb5a24d7f692ad129f019f3b670531eccfe14415 | |
| author | Hanna Reitz <hreitz@redhat.com> | |
| Wed, 17 Nov 2021 15:17:06 +0000 (17 16:17 +0100) | ||
| committer | Hanna Reitz <hreitz@redhat.com> | |
| Tue, 23 Nov 2021 14:39:12 +0000 (23 15:39 +0100) | ||
| tree | f53a840f620d7efcb12840a4ca01c54813300c51 | treesnapshot (tar.gz zip) |
| parent | 22c36b75c8a07f34a6516a8d79f38c74530727a1 | commitdiff |
iotests: Use aes-128-cbc
Our gnutls crypto backend (which is the default as of 8bd0931f6)
supports neither twofish-128 nor the CTR mode. CBC and aes-128 are
supported by all of our backends (as far as I can tell), so use
aes-128-cbc in our iotests.
(We could also use e.g. aes-256-cbc, but the different key sizes would
lead to different key slot offsets and so change the reference output
more, which is why I went with aes-128.)
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
Message-Id: <20211117151707.52549-2-hreitz@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Tested-by: Thomas Huth <thuth@redhat.com>
Our gnutls crypto backend (which is the default as of 8bd0931f6)
supports neither twofish-128 nor the CTR mode. CBC and aes-128 are
supported by all of our backends (as far as I can tell), so use
aes-128-cbc in our iotests.
(We could also use e.g. aes-256-cbc, but the different key sizes would
lead to different key slot offsets and so change the reference output
more, which is why I went with aes-128.)
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
Message-Id: <20211117151707.52549-2-hreitz@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Tested-by: Thomas Huth <thuth@redhat.com>
| tests/qemu-iotests/206 | diffblobblamehistory | |
| tests/qemu-iotests/206.out | diffblobblamehistory | |
| tests/qemu-iotests/210 | diffblobblamehistory | |
| tests/qemu-iotests/210.out | diffblobblamehistory |