Summary: SELinux is preventing /usr/bin/perl "write" access on psad. Detailed Description: SELinux denied access requested by psad. It is not expected that this access is required by psad and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://docs.fedoraproject.org/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context unconfined_u:system_r:psad_t:s0 Target Context system_u:object_r:psad_etc_t:s0 Target Objects psad [ dir ] Source psad Source Path /usr/bin/perl Port <Unknown> Host (removed) Source RPM Packages perl-5.10.1-112.fc13 Target RPM Packages Policy RPM selinux-policy-3.7.19-33.fc13 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.33.5-124.fc13.x86_64 #1 SMP Fri Jun 11 09:38:12 UTC 2010 x86_64 x86_64 Alert Count 2 First Seen Thu 01 Jul 2010 09:27:27 AM CST Last Seen Thu 01 Jul 2010 10:03:53 AM CST Local ID f2796ea4-cf4d-4205-ad54-fa20cb3630c0 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1277949833.790:159): avc: denied { write } for pid=9976 comm="psad" name="psad" dev=sda3 ino=1314751 scontext=unconfined_u:system_r:psad_t:s0 tcontext=system_u:object_r:psad_etc_t:s0 tclass=dir node=(removed) type=SYSCALL msg=audit(1277949833.790:159): arch=c000003e syscall=83 success=no exit=-13 a0=2acaab0 a1=140 a2=11 a3=30c0ce8 items=0 ppid=9975 pid=9976 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="psad" exe="/usr/bin/perl" subj=unconfined_u:system_r:psad_t:s0 key=(null) Hash String generated from catchall,psad,psad_t,psad_etc_t,dir,write audit2allow suggests: #============= psad_t ============== #!!!! The source type 'psad_t' can write to a 'dir' of the following type: # psad_tmp_t #!!!! The source type 'psad_t' can write to a 'dir' of the following types: # psad_tmp_t, var_log_t #!!!! The source type 'psad_t' can write to a 'dir' of the following types: # psad_tmp_t, var_log_t, psad_var_log_t #!!!! The source type 'psad_t' can write to a 'dir' of the following types: # psad_tmp_t, var_log_t, psad_var_log_t, psad_var_lib_t #!!!! The source type 'psad_t' can write to a 'dir' of the following types: # psad_tmp_t, var_log_t, psad_var_log_t, psad_var_lib_t, psad_var_run_t #!!!! The source type 'psad_t' can write to a 'dir' of the following types: # psad_tmp_t, var_log_t, psad_var_log_t, psad_var_lib_t, psad_var_run_t, tmp_t #!!!! The source type 'psad_t' can write to a 'dir' of the following types: # psad_tmp_t, var_log_t, psad_var_log_t, psad_var_lib_t, psad_var_run_t, tmp_t, var_run_t #!!!! The source type 'psad_t' can write to a 'dir' of the following types: # psad_tmp_t, var_log_t, psad_var_log_t, psad_var_lib_t, psad_var_run_t, tmp_t, var_run_t, root_t allow psad_t psad_etc_t:dir write;
Why is 'archive' directory created in /etc/psad? Could it be moved to /var/lib/psad/ directory?
psad-2.1.7-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/psad-2.1.7-1.fc13
psad-2.1.7-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/psad-2.1.7-1.fc14
psad-2.1.7-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update psad'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/psad-2.1.7-1.fc14
psad-2.1.7-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
psad-2.1.7-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.