RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Upgrade to cryptsetup 2.0 enabling new LUKSv2 metadata format and its features.

(details will follow. I'll add individual feature descriptions for testing)

Hi Ondrej,
could you please describe new features in cryptsetup 2.0?
How will customers upgrading from cryptsetup-1.7.4 to cryptsetup 2.0 be affected?
Is there any work needed to be done on other components (for example python-blivet/anaconda)?
Thank you.

It has to be at least 2.0.3 because that version contains code that is better aware of NBDE additional metadata created by luksmeta package.

https://mirrors.edge.kernel.org/pub/linux/utils/cryptsetup/v2.0/v2.0.3-ReleaseNotes

Is that rebase switching the tool to use argon2 by default?

No. In RHEL7 LUKS1 format is (and will be) default and it doesn't use argon2 kdf.

cryptsetup-2.0.3-1.el7.x86_64 is already in the distro.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3239