Summary: SELinux is preventing /usr/sbin/sshd "module_request" access. Detailed Description: SELinux denied access requested by sshd. It is not expected that this access is required by sshd 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:sshd_t:s0-s0:c0.c1023 Target Context system_u:system_r:kernel_t:s0 Target Objects None [ system ] Source sshd Source Path /usr/sbin/sshd Port <Unknown> Host (removed) Source RPM Packages openssh-server-5.2p1-31.fc12 Target RPM Packages Policy RPM selinux-policy-3.6.32-46.fc12 Selinux Enabled True Policy Type targeted MLS Enabled True Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.5-127.fc12.x86_64 #1 SMP Sat Nov 7 21:11:14 EST 2009 x86_64 x86_64 Alert Count 25 First Seen Mon 16 Nov 2009 03:39:47 PM EST Last Seen Thu 19 Nov 2009 08:32:35 AM EST Local ID 82e9f9b3-5225-41e3-90c4-0c1c71d6db0b Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1258637555.886:17): avc: denied { module_request } for pid=1294 comm="sshd" scontext=system_u:system_r:sshd_t:s0-s0:c0.c1023 tcontext=system_u:system_r:kernel_t:s0 tclass=system node=(removed) type=SYSCALL msg=audit(1258637555.886:17): arch=c000003e syscall=41 success=no exit=-97 a0=a a1=1 a2=6 a3=fffffffffffffee8 items=0 ppid=1 pid=1294 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="sshd" exe="/usr/sbin/sshd" subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 key=(null) Hash String generated from selinux-policy-3.6.32-46.fc12,catchall,sshd,sshd_t,kernel_t,system,module_request audit2allow suggests: #============= sshd_t ============== allow sshd_t kernel_t:system module_request;
*** This bug has been marked as a duplicate of bug 527936 ***