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.
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/kerb-nfs.html
Section Number and Name:
Chapter 18.3.1 Step 8 "Edit the /etc/exports file and add the Kerberos information:"
Describe the issue:
in our documentation it describe how to export the export with sec=sys AND with sec=krb5[i|p], so it offers this for copy and paste:
/export *(rw,sec=sys:krb5:krb5i:krb5p)
From my point of view this is but, because it is not adding any security to your environment as any not-so-kind-user, that is not voluntarily using kerberos, can mount the share with sec=sys and as we put the star in front, nearly everyone can mount the share.
I agree, that this will not be done by the automounting IPA-clients that are configured according to our further documentation, but as I said: this leaves the door really wide open, AND there is no need for it.
Suggestions for improvement:
change it to:
/export *(rw,sec=krb5:krb5i:krb5p)
Additional information: