Summary: SELinux is preventing /usr/sbin/pppd "read write" access on pppd2.tdb. Detailed Description: SELinux denied access requested by pppd. It is not expected that this access is required by pppd 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://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context system_u:system_r:pppd_t:s0 Target Context unconfined_u:object_r:var_run_t:s0 Target Objects pppd2.tdb [ file ] Source pppd Source Path /usr/sbin/pppd Port <Unknown> Host (removed) Source RPM Packages ppp-2.4.4-13.fc12 Target RPM Packages Policy RPM selinux-policy-3.6.32-41.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux localhost.localdomain 2.6.31.5-127.fc12.i686.PAE #1 SMP Sat Nov 7 21:25:57 EST 2009 i686 i686 Alert Count 1 First Seen Sat 13 Feb 2010 03:42:16 PM CET Last Seen Sat 13 Feb 2010 03:42:16 PM CET Local ID 7b303054-78f1-45ec-90c4-86571fce49c2 Line Numbers Raw Audit Messages node=localhost.localdomain type=AVC msg=audit(1266072136.691:45922): avc: denied { read write } for pid=5132 comm="pppd" name="pppd2.tdb" dev=dm-0 ino=2621950 scontext=system_u:system_r:pppd_t:s0 tcontext=unconfined_u:object_r:var_run_t:s0 tclass=file node=localhost.localdomain type=SYSCALL msg=audit(1266072136.691:45922): arch=40000003 syscall=5 success=no exit=-13 a0=165513 a1=42 a2=1a4 a3=0 items=0 ppid=1196 pid=5132 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="pppd" exe="/usr/sbin/pppd" subj=system_u:system_r:pppd_t:s0 key=(null) Hash String generated from catchall,pppd,pppd_t,var_run_t,file,read,write audit2allow suggests: #============= pppd_t ============== allow pppd_t var_run_t:file { read write };
*** This bug has been marked as a duplicate of bug 560014 ***