I just got this
For all SELinux alerts I just enter the suggested commands and get on with my live.
Is this the way to handle SELinux alerts? or should I be worried.
Entering the suggested commands creates a local policy and next time snapperd will be allowed its action because you allowed it in your custom policy module.
However, if you think it’s a bug, devs and authors of selinux-policy won’t learn about it, can’t examine it further and add the exception to the next release of selinux-policy.
I’d suggest you report this by filing a bug against selinux-policy and let someone have a look if snapperd should be allowed to write to info.xml.tmp-…
If you simply ignore the SELinux access violations and allow everything anyway, what’s the point of keeping it enabled? You might as well switch it to permissive then or even disable it entirely.
2 Likes
My thoughts exactly. I’m not sure what is a bug or what is expected behaviour.
Therefore I was suggesting to file a bug so someone can take a look at.
2 Likes