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

[Luca Boccassi]

Public bug reported:

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

** Also affects: lvm2 (Ubuntu Noble)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/2054620

Title:
  libdm returns wrong error code when dm-verity key cannot be found

Status in lvm2 package in Ubuntu:
  New
Status in lvm2 source package in Noble:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions