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:
pkispawn generates 'INFO: FIPS Mode: True' even if the FIPS mode is not enabled on the machine
Version-Release number of selected component (if applicable):
pki-core-10.10.2-1.module+el8.4.0+9165+77c6d399.src.rpm
How reproducible:
Always
Steps to Reproduce:
1. Check FIPS mode is enabled or not
# fips-mode-setup --check
Installation of FIPS modules is not completed.
FIPS mode is disabled.
2. pkispawn subsystem with --debug
3. The spawn logs will generate 'INFO: FIPS Mode: True'
Actual results:
The spawn log shows 'INFO: FIPS Mode: True' for non-fips machine
Expected results:
spawn log should print 'INFO: FIPS Mode: False' for non-fips machine and vice-versa
Additional info:
Tested on RHEL bits:
[root@pki1 ~]# rpm -qi pki-ca
Name : pki-ca
Version : 10.10.3
Release : 1.module+el8.4.0+9456+88377f87
Architecture: noarch
Install Date: Thu 21 Jan 2021 04:43:15 AM EST
Group : Unspecified
Size : 3202831
License : GPLv2 and LGPLv2
Signature : RSA/SHA256, Wed 20 Jan 2021 12:14:04 PM EST, Key ID 199e2f91fd431d51
Source RPM : pki-core-10.10.3-1.module+el8.4.0+9456+88377f87.src.rpm
Build Date : Thu 14 Jan 2021 03:17:34 PM EST
Build Host : arm64-026.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor : Red Hat, Inc.
URL : https://www.dogtagpki.org
Summary : PKI CA Package
Proof of concept:
The downstream pipeline triggered on RHEL bits and working fine:
https://gitlab.cee.redhat.com/prisingh/pki-pytest-ansible/-/pipelines/906244
Hence, Marking this Bugzilla as verified.
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 (Moderate: pki-core:10.6 and pki-deps:10.6 security, 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/RHSA-2021:1775