Hide Forgot
Description of problem: SELinux is preventing /usr/sbin/ebtables from read, write access on the file /tmp/ffivoqLvr (deleted). ***** Plugin leaks (86.2 confidence) suggests ****************************** If you want to ignore ebtables trying to read write access the ffivoqLvr (deleted) file, because you believe it should not need this access. Then you should report this as a bug. You can generate a local policy module to dontaudit this access. Do # grep /usr/sbin/ebtables /var/log/audit/audit.log | audit2allow -D -M mypol # semodule -i mypol.pp ***** Plugin catchall (14.7 confidence) suggests *************************** If you believe that ebtables should be allowed read write access on the ffivoqLvr (deleted) file 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 ebtables /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:iptables_t:s0 Target Context system_u:object_r:firewalld_tmpfs_t:s0 Target Objects /tmp/ffivoqLvr (deleted) [ file ] Source ebtables Source Path /usr/sbin/ebtables Port <Unknown> Host (removed) Source RPM Packages ebtables-2.0.10-6.fc18.i686 Target RPM Packages Policy RPM selinux-policy-3.11.1-106.fc18.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.11.9-100.fc18.i686 #1 SMP Wed Nov 20 22:13:27 UTC 2013 i686 i686 Alert Count 1 First Seen 2013-12-03 22:07:26 EST Last Seen 2013-12-03 22:07:26 EST Local ID 99c572f1-622c-4dbe-8108-deba8b1011ee Raw Audit Messages type=AVC msg=audit(1386126446.246:728): avc: denied { read write } for pid=2675 comm="ebtables" path=2F746D702F666669766F714C7672202864656C6574656429 dev="tmpfs" ino=27622 scontext=system_u:system_r:iptables_t:s0 tcontext=system_u:object_r:firewalld_tmpfs_t:s0 tclass=file type=SYSCALL msg=audit(1386126446.246:728): arch=i386 syscall=execve success=yes exit=0 a0=931cbe0 a1=931d1f0 a2=930ccd0 a3=1 items=0 ppid=664 pid=2675 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=ebtables exe=/usr/sbin/ebtables subj=system_u:system_r:iptables_t:s0 key=(null) Hash: ebtables,iptables_t,firewalld_tmpfs_t,file,read,write audit2allow #============= iptables_t ============== allow iptables_t firewalld_tmpfs_t:file { read write }; audit2allow -R require { type firewalld_tmpfs_t; type iptables_t; class file { read write }; } #============= iptables_t ============== allow iptables_t firewalld_tmpfs_t:file { read write }; Additional info: reporter: libreport-2.1.9 hashmarkername: setroubleshoot kernel: 3.11.9-100.fc18.i686 type: libreport
THis is firewalld leaking its tmpfs file to other commands.
Which firewalld version is installed? What have been done at this time with firewalld?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.