3 ms·
SELinux can't tell which of those accesses were intended, and which were actual security violations it should keep preventing. That requires human intervention.
by yorwba 9y ago
SELinux can't tell which of those accesses were intended, and which were actual security violations it should keep preventing. That requires human intervention.
Maybe it could be made more convenient by a tool that parses the log and automatically runs the commands when you answer the question with "y".
- naasking 9y ago> SELinux can't tell which of those accesses were intended, and which were actual security violations it should keep preventing. That requires human intervention. Right, it requires intervention by a person who doesn't actually understand the minutiae of what the software is trying to do, so obviously they can make a properly informed choice as to what is and is not a security violation. Modern operating systems are so broken...