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.
DescriptionCharles Stewart
2011-09-15 14:29:28 UTC
Description of problem:
Default prelink configuration does not blacklist crypto binaries checked by fipscheck. Failing to blacklist these crypto binaries causes /etc/cron.daily/prelink to prelink the binaries, changing the hmac signature of the files and breaking their validation according to fipscheck.
Version-Release number of selected component (if applicable):
prelink-0.4.4-1.el6
How reproducible:
Every time.
Steps to Reproduce:
1. Install base system
2. run /etc/cron.daily/prelink as root
3. FIPSCHECK_DEBUG=stderr fipscheck /usr/bin/fipscheck
Actual results:
fipscheck validation returns with error code 14 and stderr output indicates failure to initialize fips mode within openssl for /usr/bin/fipscheck
Expected results:
Return code 0 indicating binary matches corresponding hmac in /usr/bin/.fipscheck.hmac
Additional info:
Can be fixed by removing temporarily undoing the prelinking of the system by executing `prelink -au` then add the following to the tail of /etc/prelink.conf:
cat /etc/prelink.conf <<EOF
# the following binaries are blacklisted from prelinking due to
# their security relevance according to FIPS. Once deployed,
# they cannot be modified or their HMACs are no longer valid.
-b /lib{,64}/libcryptsetup.so*
-b /lib{,64}/libgcrypt.so*
-b /lib{,64}/libfipscheck.so*
-b /usr/lib{,64}/libcrypto.so*
-b /usr/lib{,64}/libssl.so*
-b /sbin/cryptsetup
-b /usr/bin/fipscheck
-b /usr/bin/openssl
-b /usr/sbin/sshd
-b /usr/bin/ssh
-b /usr/bin/ssh-add
-b /usr/bin/ssh-agent
-b /usr/bin/ssh-keygen
-b /usr/bin/ssh-keyscan
EOF
The next time the daily cron job is run, the system will be prelinked again without modifying fipscheck relevant binaries.
No, that was not accepted by the FIPS certification lab. Currently all the security policies of the FIPS modules state that prelink must be switched off.
It also does not make any sense to prelink the binaries/libraries to undo the prelink later on each run of application that uses them anyway.
The guidance suggests switching it off completely, however the suggestion above would surely work as well. Unfortunately we cannot add this configuration as a default because it would unnecessarily make the binaries/libraries not prelinked even for non-FIPS configurations.
Description of problem: Default prelink configuration does not blacklist crypto binaries checked by fipscheck. Failing to blacklist these crypto binaries causes /etc/cron.daily/prelink to prelink the binaries, changing the hmac signature of the files and breaking their validation according to fipscheck. Version-Release number of selected component (if applicable): prelink-0.4.4-1.el6 How reproducible: Every time. Steps to Reproduce: 1. Install base system 2. run /etc/cron.daily/prelink as root 3. FIPSCHECK_DEBUG=stderr fipscheck /usr/bin/fipscheck Actual results: fipscheck validation returns with error code 14 and stderr output indicates failure to initialize fips mode within openssl for /usr/bin/fipscheck Expected results: Return code 0 indicating binary matches corresponding hmac in /usr/bin/.fipscheck.hmac Additional info: Can be fixed by removing temporarily undoing the prelinking of the system by executing `prelink -au` then add the following to the tail of /etc/prelink.conf: cat /etc/prelink.conf <<EOF # the following binaries are blacklisted from prelinking due to # their security relevance according to FIPS. Once deployed, # they cannot be modified or their HMACs are no longer valid. -b /lib{,64}/libcryptsetup.so* -b /lib{,64}/libgcrypt.so* -b /lib{,64}/libfipscheck.so* -b /usr/lib{,64}/libcrypto.so* -b /usr/lib{,64}/libssl.so* -b /sbin/cryptsetup -b /usr/bin/fipscheck -b /usr/bin/openssl -b /usr/sbin/sshd -b /usr/bin/ssh -b /usr/bin/ssh-add -b /usr/bin/ssh-agent -b /usr/bin/ssh-keygen -b /usr/bin/ssh-keyscan EOF The next time the daily cron job is run, the system will be prelinked again without modifying fipscheck relevant binaries.