Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 720462

Summary: Zarafa needs a SELinux treatment to work (currently works only in the permissive mode)
Product: Red Hat Enterprise Linux 5 Reporter: Matěj Cepl <mcepl>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: medium Docs Contact:
Priority: low    
Version: 5.6CC: david, dgunchev, dominick.grift, dwalsh, dwmw2, mcepl, mgrepl, mmalik, pcfe, redhat-bugzilla, simonhandy, stsp1, thughes, vanmeeuwen+fedora, warlord
Target Milestone: rcKeywords: Reopened, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:51c480719e17e6f8612add8e29cac913dbb73de6afef32397dc0649806675242
Fixed In Version: selinux-policy-2.4.6-318.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 574788 Environment:
Last Closed: 2012-02-21 05:47:31 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: 574788, 717158    
Bug Blocks: 726448, 758797    

Comment 4 Miroslav Grepl 2011-10-20 14:38:50 UTC 
Fixed in selinux-policy-2.4.6-318.el5
Comment 6 Matěj Cepl 2011-12-13 12:42:02 UTC 
My server is now on RHEL-6, I am not sure I will be able to verify fix.
Comment 7 Robert Scheck 2011-12-19 00:05:40 UTC 
Miroslav, is the SELinux policy regarding Zarafa same up-to-date in RHEL 5
as in RHEL 6 now?
Comment 8 Miroslav Grepl 2011-12-19 08:16:39 UTC 
Yes, it should be up-to-date.
Comment 10 errata-xmlrpc 2012-02-21 05:47:31 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-2012-0158.html