I've seen the issues with backporting the upstream fix into 2.2 and it does not look like something that is recommended. I'm working with the customer to see if the workaround of using `--disable- luks2-reencryption` to mitigate their security concerns is a good solution.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958926 Title: CVE escalation request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1958926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
