Hide Forgot
Description of problem: opendmarc seems to require a shell_exec_t when in dkim_milter_t context. Otherwise, it generates an AVC on signing messages, as follows: type=AVC msg=audit(1473957104.698:248): avc: denied { execute } for pid=1938 comm="opendmarc" name="bash" dev="vda1" ino=5442 scontext=system_u:system_r:dkim_milter_t:s0 tcontext=system_u:object_r:shell_exec_t:s0 tclass=file permissive=0 On the journal, I see this: Sep 15 16:31:44 riacho opendmarc[1198]: 8C6248108F: pclose() exited with status 127 Version-Release number of selected component (if applicable): 1.3.1, release 15.fc24 How reproducible: Always (on sending messages from a server configured with opendmarc)
I believe this bug needs to be reviewed (and addressed if necessary) in selinux-policy, so I'm re-assigning the bug to that component.
Is there anything new about this? As far as I understand, DMARC has to either be disabled for the domain or a custom selinux rule has to be added, trusting that this AVC is a false-positive. Otherwise it would generate a failure on the message envelope. In some configurations, this means a SPF failure, which is almost enough to make a message to be marked as spam on the recipient side.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Any news on this?
I tried to add a custom selinux rule to workaround this issue, but it seems that there are a lot of selinux problems with this package. Therefore, the real workaround seems to either disable opendmarc or disable selinux. Between those two, I'm disabling opendmarc.
I'd love to ship an SELinux policy with this package, but am a complete SELinux novice. If anyone would like to assist in an SELinux policy for OpenDMARC, please let me know. lvrabec: Or perhaps you could give me a nudge in the right direction, or an existing policy for a milter that I could start from?
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.