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:
When you install a new server, a certificate is generated for use on the administrative web interface. Since this is self-signed, it can be MITM'ed when connecting from non-localhost
Since we are setting up the DNS (and even populate it already with sshfp records, good job!) we should also add the TLSA record for that to _443._tcp.[KDC SERVER]
This can be done with the "tlsa" tool that is part of hash-slinger:
[root@kdc ~]# yum install hash-slinger
[...]
[root@kdc ~]# tlsa kdc.ipa.nohats.ca
Error: Answer was not DNSSEC-secure
Error: Answer was not DNSSEC-secure
[root@kdc ~]# tlsa --insecure kdc.ipa.nohats.ca
Warning: query data is not secure.
Warning: query data is not secure.
Got a certificate with Subject: /O=IPA.NOHATS.CA/CN=kdc.ipa.nohats.ca
_443._tcp.kdc.ipa.nohats.ca. IN TLSA 3 0 1 7f08fc198712cbf288d2748cd2fbf2f3ad6db8cd861a6ff98a04de3655ee224f
Got a certificate with Subject: /O=IPA.NOHATS.CA/CN=kdc.ipa.nohats.ca
_443._tcp.kdc.ipa.nohats.ca. IN TLSA 3 0 1 7f08fc198712cbf288d2748cd2fbf2f3ad6db8cd861a6ff98a04de3655ee224f
IdM team doesn't have capacity to implement this RFE for RHEL 7.4. Moving to next RHEL version. Implementing the RFE there will depend on capacity of FreeIPA upstream. Without sufficient justification there is a chance that it will be moved again later.
Once the upstream community implements this feature it will be pulled into a corresponding Red Hat Enterprise Linux release following the corresponding schedules.
From now on this issue will be tracked in the community issue tracker only.
Closing this BZ.