Bug 890647

Summary:	SELinux don't allow postqueue to run under sysadm_t
Product:	Red Hat Enterprise Linux 6	Reporter:	Filip Bartmann <filbar>
Component:	selinux-policy	Assignee:	Miroslav Grepl <mgrepl>
Status:	CLOSED ERRATA	QA Contact:	Milos Malik <mmalik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.5	CC:	dwalsh, mmalik, mtruneck
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	selinux-policy-3.7.19-223.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-21 10:12:07 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 Filip Bartmann 2012-12-28 13:01:43 UTC

Description of problem:
SELinux don't allow postqueue to run under sysadm_t


How reproducible:
Run postqueue -p with selinux in enforced mode with sysadmin_t user type.

 
Actual results:
postqueue -p
postqueue: fatal: Connect to the Postfix showq service: Permission denied

and audit2allow show:

allow sysadm_t postfix_master_t:unix_stream_socket connectto;
allow sysadm_t postfix_public_t:sock_file write;

Expected results:
Show postqueue results

Additional info:
When I add this macro:
domtrans_pattern(sysadm_t, postfix_postqueue_exec_t, postfix_postqueue_t)
then all start working fine.

Comment 2 Miroslav Grepl 2012-12-30 21:52:27 UTC

Dan added fixes to Fedora which need to be backported. Thank you for using confined users.

Comment 6 Miroslav Grepl 2013-10-15 12:58:27 UTC

#============= sysadm_t ==============

#!!!! This avc is allowed in the current policy
allow sysadm_t postfix_master_t:unix_stream_socket connectto;

Comment 9 errata-xmlrpc 2013-11-21 10:12:07 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.

http://rhn.redhat.com/errata/RHBA-2013-1598.html