Right, but *why*? I never disable SELinux and have never had an issue. Also, disabling it completely is likely not correct. If there is a specific process that SELinux doesn't play nice with, you can lower SELinux restrictiveness on a per-process level.
What process in OpenVAS does SELinux supposedly not play well with and what are the side-effects/symptoms? On Tue, May 12, 2015 at 8:07 AM, Reindl Harald <[email protected]> wrote: > > Am 12.05.2015 um 15:05 schrieb Brandon Perry: > >> Why should he do that? That seems a bit overkill? >> > > because OpenVAS should *always* run on a dedicated host / VM and deisable > SELinux was mentioned a magnitude of times by the OpenVAS developers on > that list? > > On Tue, May 12, 2015 at 2:02 AM, Eero Volotinen <[email protected] >> <mailto:[email protected]>> wrote: >> >> you should also disable selinux permanently >> > > > _______________________________________________ > Openvas-discuss mailing list > [email protected] > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > -- http://volatile-minds.blogspot.com -- blog http://www.volatileminds.net -- website
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
