Hide Forgot
The zarafa policy needs to be backported.
Fixed in selinux-policy-3.7.19-105.el6
Fixed in selinux-policy-3.7.19-107.el6
Fixed in selinux-policy-3.7.19-109.el6
Fixed in selinux-policy-3.7.19-110.el6
I'm not really happy with the SELinux policy for Zarafa. It is very incomplete; caused a lot of pain already here. Looks like I need to investigate to support you here.
Maybe we should move this to an unconfined_domain() until it gets better testing in Fedora.
Well, not sure why zarafa-deliver needs this. Does it happen by default? Or did you change your configuration.
There are various AVC denieds per default. Furthermore Zarafa is much more flexible than what the SELinux policy covers at the moment. The policy does also not cover the proprietary parts of Zarafa which are neccessary in some business installations.
Robert, could attach AVC msgs which you are getting. I really need to make zarafa domains as unconfined.
(In reply to comment #22) > I really need to make zarafa domains as unconfined. Fixed in selinux-policy-3.7.19-115.el6
Can you provide me a link to a howto how to start with a SELinux policy? So just the AVC msgs are not enough, e.g. not all Zarafa components have proper contexts.
http://people.fedoraproject.org/~dwalsh/SELinux/Presentations/PolicyGeneration.odp
(In reply to comment #25) > http://people.fedoraproject.org/~dwalsh/SELinux/Presentations/PolicyGeneration.odp I don't think that starting from the scratch is a good idea at this point. Robert, which Zarafa components are not covered?
Robert, do you use the latest RHEL6 build?
Matěj, it unfortunately feels somehow like anything. May somebody provide me the really latest SELinux policy source files for the Zarafa module?
You can get it from http://git.fedorahosted.org/git/?p=selinux-policy.git
Hi Robert, do you still see AVCs when the latest policy is installed? If so, please copy&paste them here.
type=AVC msg=audit(1321836992.613:165593): avc: denied { name_connect } for pid=1386 comm="saslauthd" dest=236 scontext=unconfined_u:system_r:saslauthd_t:s0 tcontext=system_u:object_r:zarafa_port_t:s0 tclass=tcp_socket type=SYSCALL msg=audit(1321836992.613:165593): arch=c000003e syscall=42 success=no exit=-13 a0=9 a1=89d50c a2=10 a3=7fffb909fe30 items=0 ppid=1385 pid=1386 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(n one) ses=1298 comm="saslauthd" exe="/usr/sbin/saslauthd" subj=unconfined_u:system_r:saslauthd_t:s0 key=(null) This won't be reproducible for you now as this piece of software hasn't been made public yet, but will be in the next weeks. However saslauthd_t must be able to connect to zarafa_port_t, which should be TCP ports 236/237.
Miroslav we need Mc843ff178c071c6856f7299d0c872c274cef9118 Back ported to RHEL6 F15 and F16.
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-2011-1511.html
Miroslav, any update regarding comment #37?
yes, this will be available in RHEL6.3. You can download pre-release from http://people.redhat.com/dwalsh/SELinux/RHEL6/noarch/