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.
Description of problem:
Crypto-policies rpm verify fails because nss.config is generated as a file and not a symlink like it is defined in the rpm spec
Version-Release number of selected component (if applicable):
$ rpm -qf /etc/crypto-policies/back-ends/nss.config
crypto-policies
How reproducible:
--------
# The current file, note the timestamp that will change
# ls -l /etc/crypto-policies/back-ends/nss.config
-rw-r--r--. 1 root root 429 Nov 16 19:15 /etc/crypto-policies/back-ends/nss.config
# Update the policies
# update-crypto-policies --set FUTURE
Setting system policy to FUTURE
Note: System-wide crypto policies are applied on application start-up.
It is recommended to restart the system for the change of policies
to fully take place.
# Now the file is re-generated
# ls -l /etc/crypto-policies/back-ends/nss.config
-rw-r--r--. 1 root root 370 Nov 16 19:17 /etc/crypto-policies/back-ends/nss.config
# And it is again failing the rpm verify
# rpm -V crypto-policies
.M....... c /etc/crypto-policies/back-ends/nss.config
# Because it is now a file and not a symlink anymore
# rpm -qlv crypto-policies | grep back-ends/nss.config
lrwxrwxrwx 1 root root 42 Jul 13 16:04 /etc/crypto-policies/back-ends/nss.config -> /usr/share/crypto-policies/DEFAULT/nss.txt
----------
Additional info:
Account : HILTI AG
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 (crypto-policies 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-2021:4460