ifconfig behavior being flagged by SELinux

Latest response

Where can I find out what ifconfig is trying to do that is causing a bunch of SELinux errors? Ideally, if ifconfig is supposed to be able to do what it's trying to do, I would like to add a policy for SELinux to allow it. Otherwise, if it's not supposed to be able to do whatever it's trying to do, I'd prefer to leave the access denied, but no longer audit for it.

 

Here is the AVC message from avcsearch:

 

type=AVC msg=audit(1340051529.337:1067312): avc: denied { read write } for pid=10289 comm="ifconfig" path="socket:[25431745]" dev=sockfs ino=25431745 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:initrc_t:s0 tclass=tcp_socket

DC

Responses