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.
Bug 2193342 - LUKS devices created during installation in FIPS mode use argon2i derivation function
Summary: LUKS devices created during installation in FIPS mode use argon2i derivation ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cryptsetup
Version: 8.8
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: 8.9
Assignee: Daniel Zaťovič
QA Contact: guazhang@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-05 10:18 UTC by Jan Stodola
Modified: 2023-11-14 18:12 UTC (History)
6 users (show)

Fixed In Version: cryptsetup-2.3.7-7.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-14 15:51:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab cryptsetup cryptsetup merge_requests 365 0 None merged Delagate FIPS mode detection to configured crypto backend. 2023-05-05 13:02:05 UTC
Red Hat Issue Tracker RHELPLAN-156500 0 None None None 2023-05-05 10:19:08 UTC
Red Hat Product Errata RHBA-2023:7161 0 None None None 2023-11-14 15:51:17 UTC

Description Jan Stodola 2023-05-05 10:18:23 UTC 
Description of problem:
When installing a system in FIPS mode and creating LUKS devices, the installer creates LUKS devices having the argon2i key derivation function. pbkdf2 should be used instead in FIPS mode (see bug 1584710).

Version-Release number of selected component (if applicable):
cryptsetup-2.3.7-5.el8 from RHEL-8.8, but the same problem exists since RHEL-8.0 (cryptsetup-2.0.6-1.el8.x86_64.rpm)

How reproducible:
Always

Steps to Reproduce:
1. Start the installation in FIPS mode (with "fips=1" on the kernel cmdline)
2. Let anaconda create an encrypted partition
3. Check the created encrypted partition

Actual results:
[anaconda root@localhost ~]# cryptsetup luksDump /dev/vda2 
LUKS header information
Version:        2
Epoch:          3
Metadata area:  16384 [bytes]
Keyslots area:  16744448 [bytes]
UUID:           3f8d5702-92fd-4c85-80c2-341b292610c6
Label:          (no label)
Subsystem:      (no subsystem)
Flags:          (no flags)

Data segments:
  0: crypt
        offset: 16777216 [bytes]
        length: (whole device)
        cipher: aes-xts-plain64
        sector: 512 [bytes]

Keyslots:
  0: luks2
        Key:        512 bits
        Priority:   normal
        Cipher:     aes-xts-plain64
        Cipher key: 512 bits
        PBKDF:      argon2i
        Time cost:  4
        Memory:     1048576
        Threads:    2
...


Expected results:
PBKDF:   pbkdf2

Additional info:
* There is no /etc/system-fips in the installation environment in FIPS mode.
* Manually creating an empty /etc/system-fips file in the installation environment is a workaround for the installer to create LUKS devices with pbkdf2
* The same problem exists in the installation environment when running cryptsetup manually, like cryptsetup luksFormat $device.
* This is not a problem on the installed system, since /etc/system-fips exists there in FIPS mode.
Comment 4 Ondrej Kozina 2023-05-11 09:48:17 UTC 
After the installation it can be fixed by running following command:

cryptsetup luksConvertKey -S<keyslot_id> /dev/vda2

The command above will change pbkdf parameters to appropriate default values (pbkdf2 function, targeting 2 seconds unlock time if system runs in FIPS mode) for keyslot identified by <keyslot_id>. The keyslot binary area is overwritten with new data containing same volume key but it will be protected by new KEK derived from passphrase using pbkdf2 function.
Comment 9 errata-xmlrpc 2023-11-14 15:51:13 UTC 
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 (cryptsetup bug fix and enhancement update), 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-2023:7161
Note You need to log in before you can comment on or make changes to this bug.