Hide Forgot
Description of problem: I downloaded the source for sagan I built and installed sagan per https://wiki.quadrantsec.com/twiki/bin/view/Main/SaganInstall Created the sagan fifo and rsyslog config file for sagan restarted rsyslog. Even after I created the local policy I continue to get the alerts SELinux is preventing /usr/sbin/rsyslogd from 'open' accesses on the fifo_file /run/sagan.fifo. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that rsyslogd should be allowed open access on the sagan.fifo fifo_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 72733A6D61696E20513A526567 /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:syslogd_t:s0 Target Context unconfined_u:object_r:var_run_t:s0 Target Objects /run/sagan.fifo [ fifo_file ] Source 72733A6D61696E20513A526567 Source Path /usr/sbin/rsyslogd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.12.1-74.10.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.11.6-200.fc19.x86_64 #1 SMP Fri Oct 18 22:34:18 UTC 2013 x86_64 x86_64 Alert Count 20 First Seen 2013-10-26 15:33:29 PDT Last Seen 2013-10-26 16:01:34 PDT Local ID 6bc5f290-d03b-4ae5-9d89-5bebf41eaeee Raw Audit Messages type=AVC msg=audit(1382828494.72:723): avc: denied { open } for pid=537 comm=72733A6D61696E20513A526567 path="/run/sagan.fifo" dev="tmpfs" ino=230177 scontext=system_u:system_r:syslogd_t:s0 tcontext=unconfined_u:object_r:var_run_t:s0 tclass=fifo_file Hash: 72733A6D61696E20513A526567,syslogd_t,var_run_t,fifo_file,open Additional info: reporter: libreport-2.1.8 hashmarkername: setroubleshoot kernel: 3.11.6-200.fc19.x86_64 type: libreport
If you run in permissive mode could you add the AVC's that you see.
I'm not sure what you asking for, the AVC I'm getting is listed in the problem description.
Try again but this time run the system in permissive mode. The problem is we don't have policy for sagan, which to SELinux looks like syslogd daemon is talking to a random fifo_file in /run directory.
There is an SElinux policy for snort even though F19 doesn't provide snort. If I change the mode to permissive I don't get any alerts regarding the access to the fifo.
Is snort and sagan related, Can I just label sagan process as if it was snort, from a security point of view.
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.