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 accessing an NFS4+KRB5 share rpc.gssd attempts to fork and SUID an
instance of itself to the user that wants to access the share. The current SELinux
policy forbids this.
Version-Release number of selected component (if applicable):
selinux-policy-3.12.1-103.el7.noarch
How reproducible:
Steps to Reproduce:
1. Mount an NFS4 share with sec=krb5
Actual results:
Access fails.
Expected results:
Mount works and a new rpc.gssd running as the user can be found.
Additional information:
SELinux is preventing /usr/sbin/rpc.gssd from using the setgid capability. For complete SELinux messages.
# audit2allow -Ra
require {
type gssd_t;
class capability setgid;
}
#============= gssd_t ==============
allow gssd_t self:capability setgid;
commit 357fcb0c57fe768d1f553a9a5afa0c4ab9b5c241
Author: Miroslav Grepl <mgrepl>
Date: Tue Jan 7 09:04:13 2014 +0100
Add setgid cap for rpc.gssd to make NFS4+KRB5 share working
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: When accessing an NFS4+KRB5 share rpc.gssd attempts to fork and SUID an instance of itself to the user that wants to access the share. The current SELinux policy forbids this. Version-Release number of selected component (if applicable): selinux-policy-3.12.1-103.el7.noarch How reproducible: Steps to Reproduce: 1. Mount an NFS4 share with sec=krb5 Actual results: Access fails. Expected results: Mount works and a new rpc.gssd running as the user can be found. Additional information: SELinux is preventing /usr/sbin/rpc.gssd from using the setgid capability. For complete SELinux messages. # audit2allow -Ra require { type gssd_t; class capability setgid; } #============= gssd_t ============== allow gssd_t self:capability setgid;