[Bug 2054620] [NEW] libdm returns wrong error code when dm-verity key cannot be found

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Luca Boccassi (bluca):

When libcryptsetup tries to activate a signed dm-verity volume, and the
key is not in the kernel keyring, libdevicemapper does not return the
appropriate ENOKEY, so the failure cannot be distinguished from other
generic issues.

This is fixed in the lvm2 version 2.03.23 upstream release.

Please consider backporting this patch for Noble.

Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3
Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1

** Affects: lvm2 (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: lvm2 (Ubuntu Noble)
     Importance: Undecided
         Status: New


** Tags: patch patch-accepted-upstream
-- 
libdm returns wrong error code when dm-verity key cannot be found
https://bugs.launchpad.net/bugs/2054620
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.