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.
DescriptionFlorence Blanc-Renaud
2020-08-19 14:12:05 UTC
This bug is created as a clone of upstream ticket:
https://pagure.io/freeipa/issue/8441
### Issue
On a CA-ful installation /etc/ipa/ca.crt has mode 0644. On a CA-less installation it is 0444.
This inconsistency raises a false positive for freeipa-healthcheck.
In a CA-less environment the CA certificate is created at https://pagure.io/freeipa/blob/master/f/ipaserver/install/server/install.py#_909 prior to DS installation but then overwritten at the end of init_from_pkcs12 in export_ca_cert https://pagure.io/freeipa/blob/master/f/ipaserver/install/certs.py#_325 The original creation is probably not necessary at all. The cert is created in both cases 0444.
In a CA-ful environment the CA certificate is created by the pkispawn as 0644.
I don't have strong feelings either way which one is correct. The file is owned by root so the write mode is a no-op. I'm inclined to make it 0644 since there are more existing CA-ful installations.
It is TBD whether the initial creation is needed or not. If it isn't needed then those lines should be removed.
I don't see a need for an upgrader to fix existing perms. It is just a warning from healthcheck in any case.
Comment 1Florence Blanc-Renaud
2020-08-19 14:14:10 UTC
Fixed upstream:
master:
ec367aa Set mode of /etc/ipa/ca.crt to 0644 in CA-less installations
7e37b45 ipatests: Check permissions of /etc/ipa/ca.crt new installations
ipa-4-8:
4a97145 Set mode of /etc/ipa/ca.crt to 0644 in CA-less installations
da2079c ipatests: Check permissions of /etc/ipa/ca.crt new installations
Upstream test added in ipatests/test_integration/test_caless.py and ipatests/test_integration/test_installation.py
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: idm:DL1 and idm:client 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-2020:4670