Hide Forgot
Description of problem: SELinux is preventing /usr/sbin/winbindd from using the 'signull' accesses on a process. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that winbindd should be allowed signull access on processes labeled kernel_t 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 winbindd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:winbind_t:s0 Target Context system_u:system_r:kernel_t:s0 Target Objects [ process ] Source winbindd Source Path /usr/sbin/winbindd Port <Unknown> Host (removed) Source RPM Packages samba-winbind-4.0.7-2.fc19.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-66.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.10.3-300.fc19.x86_64 #1 SMP Fri Jul 26 00:00:58 UTC 2013 x86_64 x86_64 Alert Count 1 First Seen 2013-08-04 21:01:33 EDT Last Seen 2013-08-04 21:01:33 EDT Local ID 389cda37-721f-449f-8ba0-fd4e392ae187 Raw Audit Messages type=AVC msg=audit(1375664493.46:2403): avc: denied { signull } for pid=928 comm="winbindd" scontext=system_u:system_r:winbind_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process type=SYSCALL msg=audit(1375664493.46:2403): arch=x86_64 syscall=kill success=no exit=EACCES a0=45e2 a1=0 a2=0 a3=49 items=0 ppid=1 pid=928 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=winbindd exe=/usr/sbin/winbindd subj=system_u:system_r:winbind_t:s0 key=(null) Hash: winbindd,winbind_t,kernel_t,process,signull Additional info: reporter: libreport-2.1.9 hashmarkername: setroubleshoot kernel: 3.11.6-200.fc19.x86_64 type: libreport
Any idea what is going on here? Why is winbind sending a signull to a kernel process?
*** Bug 1083591 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.