4 ms·
It's been years since I was responsible for administering Linux Servers, but half the issues I ran into were generally fixed with `restorecon`. I used to be th
by evanreichard 4y ago
It's been years since I was responsible for administering Linux Servers, but half the issues I ran into were generally fixed with `restorecon`.
I used to be that "never disable SELinux" person, but I've since become a bit more pragmatic. But I still think you should at least spend a bit of time trying to get it to work before defaulting to `setenforce 0`.
I'm a Detection and Response Engineer now, Analyst for several years prior, and I've seen several incidents that would have been stopped by SELinux. Almost all of them were web shells or web app based RCEs. E.g. https://nvd.nist.gov/vuln/detail/cve-2019-3396 https://nvd.nist.gov/vuln/detail/cve-2019-3396
- bravetraveler 4y agoYea, pretty much. Restoring the defined contexts is the appropriate method -- the policy modifications to make $service work should be well defined at the time of integration, never a surprise. If something is suddenly breaking because it needs to break a new policy, that's a problem with the processes being followed or the software; not SELinux.