> We don't support SELinux in Ubuntu (only AppArmor), That sounds more than strange: There are many hints, that Ubuntu (also) supports SELinux [1] [2].
I'm not sure how you work together with the people of AppArmor or SELinux: typically the application developers / maintainers should discuss the MAC rules with the maintainers of the appropriate MAC implementation (because those are the people who should know what the application should be allowed to). Therefore my idea was, that you tell those people: my application needs those rules , please implement them. One thing I could imagine (after reading your answer) is, that this bug might be related to the selinux-policy-default package? I'm somewhat convinced, that the problem is Ubuntu-related: the appropriate policy packages were especially created for Debian / Ubuntu - this has nothing to do with the upstream systemd (therefore I see no sense in reporting this there). (I have a running Debian Jessie using systemd with SELinux set to enforcing for a year now - without these problems.) Would it be possible that you discuss this with the SELinux-Ubuntu people, how to handle such kind of problem? [1] https://wiki.ubuntu.com/Security/Features [2] http://packages.ubuntu.com/search?keywords=selinux&searchon=names&suite=xenial§ion=all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563354 Title: systemd-tmpfiles-setup.service fails after switching SELinux to enforcing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1563354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
