> Hey Casper! I ended up finding out what my problem was. The policy I had mentioned trying in my first post ended up being correct after all. It turned out that I had a rogue ejabberd policy in the system in addition to the policy I was testing, and the rogue policy had higher priority than the one provided by the RPM ☹ I must have installed this policy by hand some time in the past and forgotten to remove it. After removing it, I found that I just needed one more line on the policy to address this issue: https://src.fedoraproject.org/rpms/ejabberd/c/d48066216cac7e2ec1626d65376313dc12e9477f?branch=rawhide With this policy I am able to run ejabberd with STUN/TURN enabled and with the nis_enabled bool disabled. There are updates for F33-36 in Bodhi now: https://bodhi.fedoraproject.org/updates/?packages=ejabberd
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ selinux mailing list -- selinux@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to selinux-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/selinux@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
