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.
https://fedorahosted.org/freeipa/ticket/4310
The setup for Kerberized NFS is (potentially) wrong. From the ticket:
1.Get credentials from Kerberos.
[root@server ~]#kinit admin
2.On a FreeIPA server, add an NFS service principal for the NFS client.
[root@server ~]# ipa service-add nfs/ipaclient.example.com@EXAMPLE
3.On the FreeIPA server, obtain a keytab for the NFS service principal.
[root@server ~]# ipa-getkeytab -s ipaserver.example.com -p nfs/ipaclient.example.com@EXAMPLE -k /tmp/krb5.keytab
4.Copy the keytab from the FreeIPA server to the NFS server. For example, if the FreeIPA and NFS servers are on different machines:
[root@server ~]# scp /tmp/krb5.keytab root.com:/etc/krb5.keytab
5.Copy the keytab from the FreeIPA server to the FreeIPA client. For example:
[root@server ~]# scp /tmp/krb5.keytab root.com:/etc/krb5.keytab
These instructions are directing the users to overwrite the existing /etc/krb5.keytab. They should read:
1.On a FreeIPA server, add an NFS service principal for the NFS client.
[root@ipaserver ~]# ipa service-add nfs/ipaclient.example.com@EXAMPLE
2.On the NFS server, acquire credentials from Kerberos:
[root@nfsserver ~]#kinit admin
3.On the NFS server, obtain a keytab for the NFS service principal.
[root@nfsserver ~]# ipa-getkeytab -s ipaserver.example.com -p nfs/ipaclient.example.com@EXAMPLE -k /etc/krb5.keytab
These instructions have ssevetral issues.
1.They suggest to create keys in /tmp
FIix: always create keys in /root
2.They suggest to create the nfs ser ver keytab on a host that is not the server.
Fix: suggest strongly to run ipa-getkeytab directly on the target host so keys do not risk to be exposed 'in transit', ipa-getkeytab know how to merge new keys in krb5.keytab w/o touching pre-existing keys Fix 2. If creating the nfs keys on the target NFS server is not possible the instructions *MUST* be change to advice copying in /root of the server and include instructions on how to use ktutil to merge these keys in /etc/krb5.keytab
3.[SECURITY ISSUE] they suggest in point (5) to copy the SERVER's keys on the clients. Fix remove 5 with *extreme* prejudice.