block: an interoperability test for luks vs dm-crypt/cryptsetup
commit6278ae035fbd4bbab6a43cd53e4bf3bb71debc71
authorDaniel P. Berrange <berrange@redhat.com>
Mon, 21 Mar 2016 14:11:52 +0000 (21 14:11 +0000)
committerKevin Wolf <kwolf@redhat.com>
Wed, 30 Mar 2016 10:12:15 +0000 (30 12:12 +0200)
tree5901c57a632098ab0762e53fd2416255236e0496
parente6ff69bf5edfb0475903456a8c7f785635986540
block: an interoperability test for luks vs dm-crypt/cryptsetup

It is important that the QEMU luks implementation retains 100%
compatibility with the reference implementation provided by
the combination of the linux kernel dm-crypt module and cryptsetup
userspace tools.

There is a matrix of tests to be performed with different sets
of encryption settings. For each matrix entry, two tests will
be performed. One will create a LUKS image with the cryptsetup
tool and then do I/O with both cryptsetup & qemu-io. The other
will create the image with qemu-img and then again do I/O with
both cryptsetup and qemu-io.

The new I/O test 149 performs interoperability testing between
QEMU and the reference implementation. Such testing inherantly
requires elevated privileges, so to this this the user must have
configured passwordless sudo access. The test will automatically
skip if sudo is not available.

The test has to be run explicitly thus:

    cd tests/qemu-iotests
    ./check -luks 149

Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
tests/qemu-iotests/149 [new file with mode: 0755]
tests/qemu-iotests/149.out [new file with mode: 0644]
tests/qemu-iotests/common
tests/qemu-iotests/group