This bug was fixed in the package cryptsetup - 2:2.4.3-1ubuntu1

---------------
cryptsetup (2:2.4.3-1ubuntu1) jammy; urgency=low

  * Merge from Debian unstable (LP: #1959427). Remaining changes:
    - debian/control:
      + Recommend plymouth.
      + Depend on busybox-initramfs instead of busybox | busybox-static.
      + Move cryptsetup-initramfs back to cryptsetup's Recommends.
      + Do not build cryptsetup-suspend binary package on i386.
    - Fix cryptroot-unlock for busybox compatibility.
    - Fix warning and error when running on ZFS on root: (LP: #1830110)
      - d/functions: Return an empty devno for ZFS devices as they don't have
        major:minor device numbers.
      - d/initramfs/hooks/cryptroot: Ignore and don't print an error message
        when devices don't have a devno.
    - debian/patches/decrease_memlock_ulimit.patch
      Fixed FTBFS due to a restricted build environment
    - Stop building the udeb on request.

cryptsetup (2:2.4.3-1) unstable; urgency=high

  [ Guilhem Moulin ]
  * New upstream security release 2.4.3, with fix for CVE-2021-4122:
    decryption through LUKS2 reencryption crash recovery. (Closes: #1003685,
    #1003686)
  * Remove cryptsetup-initramfs.preinst. (Closes: #1001063)

  [ Christoph Anton Mitterer ]
  * d/rules: don't expand here-document.

 -- Steve Langasek <steve.langa...@ubuntu.com>  Fri, 28 Jan 2022
12:14:06 -0800

** Changed in: cryptsetup (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  [22.04 FEAT] Upgrade cryptsetup to latest version (crypto)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959427/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to