From: Luca Boccassi Date: Sun, 2 Oct 2022 19:12:02 +0000 (+0100) Subject: test-70: check if LUKS2 plugins are actually installed, not just supported X-Git-Tag: v252-rc1~28^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F23213%2Fhead;p=thirdparty%2Fsystemd.git test-70: check if LUKS2 plugins are actually installed, not just supported We don't build them in Debian/Ubuntu yet, even though cryptsetup supports them --- diff --git a/test/units/testsuite-70.sh b/test/units/testsuite-70.sh index 97536c812cc..b1cf7e83c4b 100755 --- a/test/units/testsuite-70.sh +++ b/test/units/testsuite-70.sh @@ -33,7 +33,8 @@ env PIN=123456 /usr/lib/systemd/systemd-cryptsetup attach test-volume $img - tpm env PIN=123457 /usr/lib/systemd/systemd-cryptsetup attach test-volume $img - tpm2-device=auto,headless=1 && { echo 'unexpected success'; exit 1; } # Check LUKS2 token plugin unlock (i.e. without specifying tpm2-device=auto) -if cryptsetup --help | grep -q 'LUKS2 external token plugin support is compiled-in'; then +if cryptsetup --help | grep -q 'LUKS2 external token plugin support is compiled-in' && \ + [ -f "$(cryptsetup --help | sed -n -r 's/.*LUKS2 external token plugin path: (.*)\./\1/p')/libcryptsetup-token-systemd-tpm2.so" ]; then env PIN=123456 /usr/lib/systemd/systemd-cryptsetup attach test-volume $img - headless=1 /usr/lib/systemd/systemd-cryptsetup detach test-volume