Bug 1139577 - [fail2ban_t] SELinux is preventing /usr/bin/python2.7 from read access on the directory .
Summary: [fail2ban_t] SELinux is preventing /usr/bin/python2.7 from read access on the...
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-09-09 09:00 UTC by Juan Orti Alcaine
Modified: 2015-06-30 01:37 UTC (History)
5 users (show)

Fixed In Version: selinux-policy-3.12.1-185.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-30 01:37:14 UTC

Attachments (Terms of Use)

Description Juan Orti Alcaine 2014-09-09 09:00:20 UTC
This is probably because I have the journal configured with Storage=volatile

SELinux is preventing /usr/bin/python2.7 from read access on the directory .

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that python2.7 should be allowed read access on the  directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# grep fail2ban-server /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:fail2ban_t:s0
Target Context                system_u:object_r:syslogd_var_run_t:s0
Target Objects                 [ dir ]
Source                        fail2ban-server
Source Path                   /usr/bin/python2.7
Port                          <Unknown>
Host                          <removed>
Source RPM Packages           python-2.7.5-13.fc20.x86_64
Target RPM Packages
Policy RPM                    selinux-policy-3.12.1-182.fc20.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     <removed>
Platform                      Linux <removed> 3.15.10-201.fc20.x86_64
                              #1 SMP Wed Aug 27 21:10:06 UTC 2014 x86_64 x86_64
Alert Count                   12
First Seen                    2014-09-09 10:21:56 CEST
Last Seen                     2014-09-09 10:54:38 CEST
Local ID                      a7e235a1-ab96-48f3-b46e-db15b719d228

Raw Audit Messages
type=AVC msg=audit(1410252878.550:728): avc:  denied  { read } for  pid=4355 comm="fail2ban-server" name="journal" dev="tmpfs" ino=9331 scontext=system_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:syslogd_var_run_t:s0 tclass=dir

type=SYSCALL msg=audit(1410252878.550:728): arch=x86_64 syscall=openat success=no exit=EACCES a0=ffffffffffffff9c a1=7fb349ab93a0 a2=90800 a3=0 items=0 ppid=1 pid=4355 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=fail2ban-server exe=/usr/bin/python2.7 subj=system_u:system_r:fail2ban_t:s0 key=(null)

Hash: fail2ban-server,fail2ban_t,syslogd_var_run_t,dir,read

Comment 1 Juan Orti Alcaine 2014-09-09 10:18:17 UTC
This rules has fixed my problems:

#============= fail2ban_t ==============
allow fail2ban_t syslogd_var_run_t:file { read open getattr };
allow fail2ban_t syslogd_var_run_t:dir read;

Comment 2 Miroslav Grepl 2014-09-09 14:02:45 UTC
#============= fail2ban_t ==============

#!!!! This avc is allowed in the current policy
allow fail2ban_t syslogd_var_run_t:dir read;

Comment 3 Lukas Vrabec 2014-09-10 09:18:49 UTC
commit 0939f216149c760434473ead133c2543fd52fb50
Author: Lukas Vrabec <lvrabec@redhat.com>
Date:   Wed Sep 10 11:18:02 2014 +0200

    Allow fail2ban read syslog pid. (#1139577)


Comment 4 Fedora Update System 2014-09-23 08:29:39 UTC
selinux-policy-3.12.1-186.fc20 has been submitted as an update for Fedora 20.

Comment 5 Fedora Update System 2014-09-25 10:45:07 UTC
Package selinux-policy-3.12.1-186.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-186.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-09-25 16:57:52 UTC
selinux-policy-3.12.1-187.fc20 has been submitted as an update for Fedora 20.

Comment 7 Fedora Update System 2014-09-30 08:36:43 UTC
selinux-policy-3.12.1-188.fc20 has been submitted as an update for Fedora 20.

Comment 8 Marcel Wysocki 2014-10-15 15:34:13 UTC
any chance this will make it into EL7?

Comment 9 Lukas Vrabec 2014-10-17 11:17:38 UTC

$ sesearch -A -s fail2ban_t -t syslogd_var_run_t -c dir 
Found 2 semantic av rules:
   allow syslog_client_type syslogd_var_run_t : dir { getattr search open } ; 
   allow fail2ban_t syslogd_var_run_t : dir { ioctl read getattr lock search open } ; 

This will be also in Rhel7.1

Comment 10 Fedora End Of Life 2015-05-29 12:49:46 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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.

Comment 11 Fedora End Of Life 2015-06-30 01:37:14 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.