Hide Forgot
Summary: SELinux is preventing /usr/bin/kpilotDaemon "read write" access on ttyS0. Detailed Description: SELinux denied access requested by kpilotDaemon. It is not expected that this access is required by kpilotDaemon 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 user_u:user_r:user_t:s0 Target Context system_u:object_r:tty_device_t:s0 Target Objects ttyS0 [ chr_file ] Source kpilotDaemon Source Path /usr/bin/kpilotDaemon Port <Unknown> Host (removed) Source RPM Packages kpilot-5.3.0-4.fc13 Target RPM Packages Policy RPM selinux-policy-3.7.19-76.fc13 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.34.7-66.fc13.i686 #1 SMP Wed Dec 15 07:40:25 UTC 2010 i686 i686 Alert Count 60393 First Seen Thu 13 Jan 2011 09:23:18 AM EST Last Seen Sun 16 Jan 2011 09:23:03 PM EST Local ID 849e41cc-f910-4d9e-a488-6939b82a838b Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1295230983.938:218121): avc: denied { read write } for pid=22993 comm="kpilotDaemon" name="ttyS0" dev=devtmpfs ino=5608 scontext=user_u:user_r:user_t:s0 tcontext=system_u:object_r:tty_device_t:s0 tclass=chr_file node=(removed) type=SYSCALL msg=audit(1295230983.938:218121): arch=40000003 syscall=5 success=no exit=-13 a0=b588f6dc a1=802 a2=310041ed a3=b588f6da items=0 ppid=1 pid=22993 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=6 comm="kpilotDaemon" exe="/usr/bin/kpilotDaemon" subj=user_u:user_r:user_t:s0 key=(null) Hash String generated from catchall,kpilotDaemon,user_t,tty_device_t,chr_file,read,write audit2allow suggests: #============= user_t ============== allow user_t tty_device_t:chr_file { read write };
What does kpilotDaemon do? Does it allocate its own tty?
Also did you run kpilotDaemon directly? --- kpilotDaemon is a program that runs in the background and handles the actual communication with the PalmPilot device. It is run automatically when needed, so you normally should not have to run it manually. ---
BTW Walt, thanks for using user_t and submitting bugs, These are very helpful for us to make a more robust environment.