Bug 622341
Summary: | SELinux is preventing /sbin/iptables-multi "read" access on /var/log/secure. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christofer C. Bell <christofer.c.bell> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | dwalsh, mgrepl, misek, russ+bugzilla-redhat |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | setroubleshoot_trace_hash:a1afe179118849220495e9e7bac95dd09fb4bb0815e69b329a79477f934460f5 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-08-10 16:58:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christofer C. Bell
2010-08-09 01:55:24 UTC
I received this alert after restarting the fail2ban service. I made a change to number of connection attempts to sshd that are allowed to fail before a ban is put in place: [root@circe fail2ban]# diff jail.conf.20100808 jail.conf 7a8,12 > ### CHANGELOG ### > # > # 08-AUG-2010, CCB -- Decreased the number of attempts sshd will allow from > # 5 to 3. > # 57c62 < maxretry = 5 --- > maxretry = 3 [root@circe fail2ban]# I then restarted the service: [root@circe fail2ban]# service fail2ban restart Stopping fail2ban: [ OK ] Starting fail2ban: [ OK ] [root@circe fail2ban]# This alert was immediately received. I am using the 3.7.19-41 release of SE Linux policy: [root@circe fail2ban]# rpm -q selinux-policy selinux-policy-3.7.19-41.fc13.noarch [root@circe fail2ban]# Which version of fail2ban do you use? You can dontaudit it using # grep iptables_t /var/log/audit/audit.log | audit2allow -D -M fail2banleak # semodule -i fail2banleak.pp I'm using fail2ban version 0.8.4-24. [cbell@circe ~]$ rpm -q fail2ban fail2ban-0.8.4-24.fc13.noarch [cbell@circe ~]$ Thank you for the tip! I'm curious with the possibility of not auditing this behavior, why the bug is closed as can't fix? Should it be opened against selinux-policy instead? Actually, it is open against selinux-policy... Anyway, the question remains. :-) There are no iptables_t entries in audit.log. That said, when I restarted the jail this time, there was no alert. The last alert was during the last reboot 4 days ago. [root@circe ~]# service fail2ban restart Stopping fail2ban: [ OK ] Starting fail2ban: [ OK ] [root@circe ~]# grep iptables_t /var/log/audit/audit.log [root@circe ~]# |