[CentOS] an actual hacked machine, in a preserved state
office at plnet.rs
Tue Jan 3 02:41:02 UTC 2012
On 01/03/2012 03:30 AM, Bennett Haselton wrote:
> In other words, when SELinux causes a problem, it can take hours or days
> to find out that SELinux is the cause -- and even then you're not done,
> because you have to figure out a workaround if you want to fix the
> problem while keeping SELinux turned on.
You can always set SELinux to permissible mode for testing purposes and
it will allow the action, but report that it would have been blocked.
(Love is in the Air)
Google is the Mother, Google is the Father, and traceroute is your
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
More information about the CentOS