Hide Forgot
SELinux is preventing /sbin/ldconfig from 'execute' accesses on the file /sbin/ldconfig. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that ldconfig should be allowed execute access on the ldconfig file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep ldconfig /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:fail2ban_t:s0 Target Context system_u:object_r:ldconfig_exec_t:s0 Target Objects /sbin/ldconfig [ file ] Source ldconfig Source Path /sbin/ldconfig Port <Unknown> Host (removed) Source RPM Packages glibc-2.13-1 Target RPM Packages glibc-2.13-1 Policy RPM selinux-policy-3.9.7-42.fc14 Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 2.6.35.13-92.fc14.i686.PAE #1 SMP Sat May 21 17:33:09 UTC 2011 i686 i686 Alert Count 2 First Seen Sun 24 Jul 2011 04:01:07 AM CEST Last Seen Mon 25 Jul 2011 09:36:12 PM CEST Local ID df061cfb-f002-40ac-ab26-9ed3e6f27101 Raw Audit Messages type=AVC msg=audit(1311622572.242:21): avc: denied { execute } for pid=1986 comm="sh" name="ldconfig" dev=dm-1 ino=1572983 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:ldconfig_exec_t:s0 tclass=file type=AVC msg=audit(1311622572.242:21): avc: denied { read open } for pid=1986 comm="sh" name="ldconfig" dev=dm-1 ino=1572983 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:ldconfig_exec_t:s0 tclass=file type=AVC msg=audit(1311622572.242:21): avc: denied { execute_no_trans } for pid=1986 comm="sh" path="/sbin/ldconfig" dev=dm-1 ino=1572983 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:ldconfig_exec_t:s0 tclass=file type=SYSCALL msg=audit(1311622572.242:21): arch=i386 syscall=execve success=yes exit=0 a0=9e3f228 a1=9e3f2a8 a2=9e3e7a8 a3=9e3f2a8 items=0 ppid=1985 pid=1986 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=ldconfig exe=/sbin/ldconfig subj=system_u:system_r:fail2ban_t:s0 key=(null) Hash: ldconfig,fail2ban_t,ldconfig_exec_t,file,execute audit2allow #============= fail2ban_t ============== allow fail2ban_t ldconfig_exec_t:file { read execute open execute_no_trans }; audit2allow -R #============= fail2ban_t ============== allow fail2ban_t ldconfig_exec_t:file { read execute open execute_no_trans };
Why is fail2ban executing ldconfig?
Not sure but we have this in Rawhide.
Ok but it looks like fail2ban is downloading stuff and then running ldconfig on it. Seems a little dangerous.
It's a while since I've used fail2ban, as it's somewhat abondonware at this point, but this is not behaviour I would expect to be seeing from this program at all.