Displaying 3 results from an estimated 3 matches for "wrongkey".
Did you mean:
wronger
2019 Nov 29
0
[PATCH] tests: test --key for a real guest (with inspection)
...ce)"
+
+# Try to decrypt the disk in different ways:
+# - pass a wrong key via stdin to check the --key value is actually used only
+# - check for /etc/fedora-release as a way to know the LUKS device was
+# decrypted correctly
+
+# Specify the libguestfs device name of the LUKS device.
+echo wrongkey | guestfish --ro -a $disk -i --keys-from-stdin \
+ --key "$device:key:FEDORA" \
+ exists /etc/fedora-release
+
+# Specify the UUID of the LUKS device.
+echo wrongkey | guestfish --ro -a $disk -i --keys-from-stdin \
+ --key "$uuid:key:FEDORA" \
+...
2019 Nov 29
1
Re: [PATCH] tests: test --key for a real guest (with inspection)
...the disk in different ways:
> +# - pass a wrong key via stdin to check the --key value is actually used only
> +# - check for /etc/fedora-release as a way to know the LUKS device was
> +# decrypted correctly
> +
> +# Specify the libguestfs device name of the LUKS device.
> +echo wrongkey | guestfish --ro -a $disk -i --keys-from-stdin \
> + --key "$device:key:FEDORA" \
> + exists /etc/fedora-release
> +
> +# Specify the UUID of the LUKS device.
> +echo wrongkey | guestfish --ro -a $disk -i --keys-from-stdin \
> + --key "$uu...
2019 Nov 29
8
[PATCH 0/1] Allow UUIDs for --key identifiers.
This combined patch series enables to decrypt LUKS devices on inspection
by allowing the UUID of the LUKS device with the --key syntax.
I opted for reusing the option instead of adding another one, as I think
that device names and UUIDs are different enough that can be properly
distinguished.
A test for this (patch #4) can be applied only when the patches for
common are applied, and the