Red Hat Bugzilla – Bug 463410
AVC Denial fail2ban
Last modified: 2009-07-31 13:37:29 EDT
Created attachment 317448 [details]
Description of problem: avc denial fail2ban
Version-Release number of selected component (if applicable):
How reproducible: F8 (samba\ssh server) always
Steps to Reproduce:
1. sshd, fail2ban, inadyn started (rl 3-5)
No avc re fail2ban
Additional info: sealert attached
restorecon -v '/var/log/fail2ban.log'
[root@server-01 ~]# audit2allow -M fail2ban < /var/log/audit/audit.log
******************** IMPORTANT ***********************
To make this policy package active, execute:
semodule -i fail2ban.pp
[root@server-01 ~]# semodule -i fail2ban.pp
libsepol.print_missing_requirements: fail2ban's global requirements were not met: type/attribute fail2ban_log_t
libsemanage.semanage_link_sandbox: Link packages failed
Created attachment 317453 [details]
Gam_server\ fail2ban avc denial
The first group of avc's are related to a leaked file descriptor in fail2ban which has already been reported. The second is caused by fail2ban trying to use a gam_server which was started by the yum daemon I believe.
It should not be using gam_server? Why is this necessary?
All of these AVC's can be ignored by the way.
When you create a custom policy module make sure it does not conflict with an existing policy module.
I always previx with my.
# audit2allow -M myfail2ban < /var/log/audit/audit.log
# semodule -i myfail2ban.pp
Otherwise you will replace the system policy module with the one you wrote and things will blow up.
(In reply to comment #2)
> The first group of avc's are related to a leaked file descriptor in fail2ban
> which has already been reported. The second is caused by fail2ban trying to
> use a gam_server which was started by the yum daemon I believe.
> It should not be using gam_server? Why is this necessary?
It was noted here:
will disable auto: and try polling see what happens
No avc denials when "polling" is used.
(Server currently down so cannot do further checking until,
new sata(s) arrive.
With polling no alerts
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. 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 '8'.
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 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
I am closing as this bug is fixed and other bugs have been reported telling fail2ban to not use gamin.