Practically there's been many examples where SELinux restricted a security vulnerability. I think SELinux is way too complicated. Needing to know exact commands to turn error messages into something understandable is bizarre.
That said, SELinux determines what is allowed. Having it introduce an additional vulnerability/permission just due to configuration is really odd.
I tried searching for your example, but can only find security bugs, not configuration issues.
That said, SELinux determines what is allowed. Having it introduce an additional vulnerability/permission just due to configuration is really odd.
I tried searching for your example, but can only find security bugs, not configuration issues.