Bug 677029

Summary: SELinux is preventing /bin/bash from 'search' accesses on the directory /home.
Product: [Fedora] Fedora Reporter: Juha Sahakangas <voas0113>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:9b1e7396cca8cf8f0af4cd7ab6863a06b809ec59d7ddf1902859fa57baa14bdb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-14 12:30:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Juha Sahakangas 2011-02-12 17:13:26 UTC
SELinux is preventing /bin/bash from 'search' accesses on the directory /home.

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

If you believe that bash should be allowed search access on the home directory 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 sh /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                unconfined_u:system_r:fail2ban_t:s0
Target Context                system_u:object_r:home_root_t:s0
Target Objects                /home [ dir ]
Source                        sh
Source Path                   /bin/bash
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           bash-4.1.7-3.fc14
Target RPM Packages           filesystem-2.4.35-1.fc14
Policy RPM                    selinux-policy-3.9.7-29.fc14
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.35.10-74.fc14.i686 #1 SMP Thu
                              Dec 23 16:17:40 UTC 2010 i686 i686
Alert Count                   1194
First Seen                    Tue 11 Jan 2011 11:28:38 EET
Last Seen                     Sat 12 Feb 2011 19:11:25 EET
Local ID                      8505445c-996a-4639-8afc-a483cfe58c7e

Raw Audit Messages
type=AVC msg=audit(1297530685.122:40667): avc:  denied  { search } for  pid=22120 comm="sh" name="/" dev=dm-2 ino=2 scontext=unconfined_u:system_r:fail2ban_t:s0 tcontext=system_u:object_r:home_root_t:s0 tclass=dir


type=SYSCALL msg=audit(1297530685.122:40667): arch=i386 syscall=stat64 success=no exit=EACCES a0=89af7f8 a1=bfa980f0 a2=99bff4 a3=0 items=0 ppid=4787 pid=22120 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=8 comm=sh exe=/bin/bash subj=unconfined_u:system_r:fail2ban_t:s0 key=(null)

Hash: sh,fail2ban_t,home_root_t,dir,search

audit2allow

#============= fail2ban_t ==============
allow fail2ban_t home_root_t:dir search;

audit2allow -R

#============= fail2ban_t ==============
allow fail2ban_t home_root_t:dir search;

Comment 1 Miroslav Grepl 2011-02-14 12:30:02 UTC
Were you sitting in your homedir when you (re)started fail2ban using

# /etc/init.d/fail2ban (re)start

If so, please use the service script

# service fail2ban (re)start

If I am wrong, please reopen the bug.