Bug 644807

Summary: smbcontrol doesn't work because selinux denies it access to pid files
Product: Red Hat Enterprise Linux 6 Reporter: RHEL Program Management <pm-rhel>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: high Docs Contact:
Priority: high    
Version: 6.0CC: azelinka, dwalsh, mgrepl, mmalik, pm-eus, snagar
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.7.19-54.el6_0.2 Doc Type: Bug Fix
Doc Text:
Due to incorrect SELinux policy, smbcontrol, a utility that sends messages to the smbd, nmbd, or winbindd service, did not work properly. This error has been fixed, the relevant policy code has been added, and SELinux no longer prevents smbcontrol from working.
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 19:01:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 634945    
Bug Blocks:    

Description RHEL Program Management 2010-10-20 11:20:37 UTC
This bug has been copied from bug #634945 and has been proposed
to be backported to 6.0 z-stream (EUS).

Comment 4 Miroslav Grepl 2010-10-20 12:30:12 UTC
Fixed in selinux-policy-3.7.19-54.el6_0.2.

Comment 6 Jaromir Hradilek 2010-10-21 08:52:45 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Due to incorrect SELinux policy, smbcontrol, a utility that sends messages to the smbd, nmbd, or winbindd service, did not work properly. This error has been fixed, the relevant policy code has been added, and SELinux no longer prevents smbcontrol from working.

Comment 9 errata-xmlrpc 2010-11-10 19:01:36 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0845.html