Bug 1139901 - SELinux is preventing /usr/bin/bash from 'search' accesses on the directory .
Summary: SELinux is preventing /usr/bin/bash from 'search' accesses on the directory .
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c3179a3c694860cfd61659f901e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-09 23:32 UTC by William Brown
Modified: 2015-06-30 01:37 UTC (History)
4 users (show)

Fixed In Version: selinux-policy-3.12.1-185.fc20
Clone Of:
Environment:
Last Closed: 2015-06-30 01:37:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description William Brown 2014-09-09 23:32:53 UTC
Description of problem:
SELinux is preventing /usr/bin/bash from 'search' accesses on the directory .

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

If you believe that bash should be allowed search 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.
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                system_u:system_r:dnssec_trigger_t:s0
Target Context                system_u:object_r:sssd_var_lib_t:s0
Target Objects                 [ dir ]
Source                        sh
Source Path                   /usr/bin/bash
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           bash-4.2.47-3.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                   9143
First Seen                    2014-07-30 14:23:40 ACST
Last Seen                     2014-09-10 09:02:13 ACST
Local ID                      511aa1b7-6a1c-4b4b-b0e0-39121da57694

Raw Audit Messages
type=AVC msg=audit(1410305533.761:482): avc:  denied  { search } for  pid=5804 comm="sh" name="sss" dev="dm-26" ino=134217872 scontext=system_u:system_r:dnssec_trigger_t:s0 tcontext=system_u:object_r:sssd_var_lib_t:s0 tclass=dir


type=SYSCALL msg=audit(1410305533.761:482): arch=x86_64 syscall=connect success=no exit=EACCES a0=4 a1=7fffc22e6260 a2=6e a3=7fffc22e5fc0 items=0 ppid=3050 pid=5804 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=sh exe=/usr/bin/bash subj=system_u:system_r:dnssec_trigger_t:s0 key=(null)

Hash: sh,dnssec_trigger_t,sssd_var_lib_t,dir,search

Additional info:
reporter:       libreport-2.2.3
hashmarkername: setroubleshoot
kernel:         3.15.10-201.fc20.x86_64
type:           libreport

Comment 1 Miroslav Grepl 2014-09-10 11:11:46 UTC
commit f0d4aff61039ca0b60034da177ff8a771038924c
Author: Miroslav Grepl <mgrepl>
Date:   Wed Sep 10 13:10:46 2014 +0200

    Call auth_use_nsswitch() for dnssec-trigger.

Comment 2 Fedora Update System 2014-09-23 08:29:41 UTC
selinux-policy-3.12.1-186.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-186.fc20

Comment 3 Fedora Update System 2014-09-25 10:45:10 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:
https://admin.fedoraproject.org/updates/FEDORA-2014-11479/selinux-policy-3.12.1-186.fc20
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2014-09-25 16:57:55 UTC
selinux-policy-3.12.1-187.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-187.fc20

Comment 5 Fedora Update System 2014-09-30 08:36:46 UTC
selinux-policy-3.12.1-188.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-188.fc20

Comment 6 Fedora End Of Life 2015-05-29 12:50:16 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 7 Fedora End Of Life 2015-06-30 01:37:17 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
bug.

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.