Bug 1044880 - SELinux is preventing /usr/sbin/rpc.gssd from using the setgid capability.
Summary: SELinux is preventing /usr/sbin/rpc.gssd from using the setgid capability.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.0
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-19 07:37 UTC by Stefan Walter
Modified: 2015-02-18 16:25 UTC (History)
2 users (show)

Fixed In Version: selinux-policy-3.12.1-116.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:26:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Stefan Walter 2013-12-19 07:37:28 UTC
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;

Comment 2 Miroslav Grepl 2014-01-07 08:05:15 UTC
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

Comment 5 Ludek Smid 2014-06-13 12:26:25 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.