Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

This is not clear. The command "cryptsetup-reencrypt" on RHEL7 has an option to create LUKS2 devices, and in RHEL7 "cryptsetup" does not accept the "reencrypt" option, so I'd say this table requires some correction.

Reported by: gpulido

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening#annotations:e97b16ab-f6f3-406d-9283-a1f954f07315

Hello,

Thank you for sharing your concern. 

The added table from the https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening is correct and applicable for RHEL 8. This link is for RHEL 8 documentation, where both the commands 'cryptsetup reencrypt' for LUKS2 format and 'cryptsetup-reencrypt' utility for LUKS1 versions are available.

The remark about RHEL 7 in the note is related to general availability of support for LUKS2 format in RHEL7 and is not related to reencryption task specifically. In RHEL 7, there is only 'cryptsetup-reencrypt' utility that triggers legacy reencryption code for both the formats.

Let us know if there is any other issue.

Thanks!

To avoid any further confusion, note related to the general availability of LUKS 2 in RHEL 7.6 has been removed from RHEL 8 and 9. Sharing the published links-

RHEL 9 - https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/security_hardening/encrypting-block-devices-using-luks_security-hardening#luks-versions-in-rhel_encrypting-block-devices-using-luks

RHEL 8 - https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/encrypting-block-devices-using-luks_security-hardening#luks-versions-in-rhel_encrypting-block-devices-using-luks

Same information is updated in the Storage title-

from storage title- 

RHEL 8- https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_storage_devices/encrypting-block-devices-using-luks_managing-storage-devices#luks-versions-in-rhel_encrypting-block-devices-using-luks

RHEL 9 - https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_storage_devices/encrypting-block-devices-using-luks_managing-storage-devices#luks-versions-in-rhel_encrypting-block-devices-using-luks

Thanks!