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.

Bug 1316724

Summary: SELinux prevents kdm from accessing /sbin/poweroff
Product: Red Hat Enterprise Linux 7 Reporter: Orion Poplawski <orion>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: low Docs Contact:
Priority: medium    
Version: 7.2CC: lvrabec, mgrepl, mmalik, orion, plautrba, pvrabec, ssekidde
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.13.1-69.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1330970 (view as bug list) Environment:
Last Closed: 2016-11-04 02:44:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Orion Poplawski 2016-03-10 22:14:12 UTC
Description of problem:

type=USER_AVC msg=audit(1457620723.473:779): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc:  denied  { status } for auid=n/a uid=0 gid=0 path="/usr/lib/systemd/system/poweroff.target" cmdline="/sbin/poweroff" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:power_unit_file_t:s0 tclass=service  exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'

I suspect this interferes with kdm's shutdown ability, but haven't tested.

See also bug #951039

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-60.el7_2.3.noarch

Comment 2 Miroslav Grepl 2016-03-14 08:16:09 UTC
Orion,
could test a local policy to see if you are able to do shutdown?

---

policy_module(myxdm, 1.0)

require {
	type xdm_t;
}

#============= xdm_t ==============
systemd_status_power_services(xdm_t)

---

# make -f /usr/share/selinux/devel/Makefile myxdm.pp
# semodule -i myxdm.pp

Comment 3 Orion Poplawski 2016-03-23 20:08:23 UTC
So it turns out that it doesn't prevent kdm from being able to do a shutdown, so not a real problem.  Addid myxdm does remove the denial though.

Comment 4 Miroslav Grepl 2016-03-31 06:41:18 UTC
Are you getting any AVCs?

Comment 5 Orion Poplawski 2016-03-31 14:27:36 UTC
Not after adding myxdm.pp.

Comment 10 errata-xmlrpc 2016-11-04 02:44:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2283.html