Bug 749674

Summary: SELinux is preventing /usr/sbin/semodule from 'write' accesses on the file /var/tmp/kdecache-alirohman/kpc/kde-icon-cache.lock (deleted).
Product: [Fedora] Fedora Reporter: Ali Rohman <alirohman>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: dominick.grift, dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:c21f0f741bf6647bbcecf9eebf6cab5c47ea50108e845c6060bbf795991f28bd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 17:20:53 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 Ali Rohman 2011-10-27 21:00:04 UTC
SELinux is preventing /usr/sbin/semodule from 'write' accesses on the file /var/tmp/kdecache-(removed)/kpc/kde-icon-cache.lock (deleted).

*****  Plugin leaks (50.5 confidence) suggests  ******************************

If you want to ignore semodule trying to write access the kde-icon-cache.lock (deleted) file, because you believe it should not need this access.
Then you should report this as a bug.  
You can generate a local policy module to dontaudit this access.
Do
# grep /usr/sbin/semodule /var/log/audit/audit.log | audit2allow -D -M mypol
# semodule -i mypol.pp

*****  Plugin catchall (50.5 confidence) suggests  ***************************

If you believe that semodule should be allowed write access on the kde-icon-cache.lock (deleted) file 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 semodule /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c102
                              3
Target Context                unconfined_u:object_r:user_tmp_t:s0
Target Objects                /var/tmp/kdecache-(removed)/kpc/kde-icon-
                              cache.lock (deleted) [ file ]
Source                        semodule
Source Path                   /usr/sbin/semodule
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           policycoreutils-2.0.86-7.fc15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.16-44.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.40.7-3.fc15.x86_64 #1 SMP Mon
                              Oct 24 13:51:56 UTC 2011 x86_64 x86_64
Alert Count                   2
First Seen                    Fri 28 Oct 2011 03:57:38 AM WIT
Last Seen                     Fri 28 Oct 2011 03:58:58 AM WIT
Local ID                      37943b27-031b-4602-8956-9e063f27ba6f

Raw Audit Messages
type=AVC msg=audit(1319749138.731:115): avc:  denied  { write } for  pid=7097 comm="semodule" path=2F7661722F746D702F6B646563616368652D616C69726F686D616E2F6B70632F6B64652D69636F6E2D63616368652E6C6F636B202864656C6574656429 dev=dm-1 ino=284183 scontext=unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=file


type=SYSCALL msg=audit(1319749138.731:115): arch=x86_64 syscall=execve success=yes exit=0 a0=10d4c00 a1=10a64a0 a2=109e830 a3=8 items=0 ppid=3170 pid=7097 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts1 ses=1 comm=semodule exe=/usr/sbin/semodule subj=unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c1023 key=(null)

Hash: semodule,semanage_t,user_tmp_t,file,write

audit2allow

#============= semanage_t ==============
allow semanage_t user_tmp_t:file write;

audit2allow -R

#============= semanage_t ==============
allow semanage_t user_tmp_t:file write;

Comment 1 Daniel Walsh 2011-10-28 12:51:34 UTC
Were you doing some kind of update when this happened?

This can be ignored since it is a leaked file descriptor or a redirection of stdout. Nothing would actually be blocked.

Comment 2 Ali Rohman 2011-11-01 11:08:21 UTC
This happen after install google chrome, and looks like chrome always crash when start, but everything allready fixed untill i upgrade my fedora 15 to fedora 16 (verne) after that chrome browser gone from my system, now i am affraid to install chrome browser again, what should i do?

Comment 3 Daniel Walsh 2011-11-01 16:41:26 UTC
You can install the chrome browser. It was not causing the problem.  We are working with the chrome browser team to make SELinux work well with their package.

Comment 4 Ali Rohman 2011-11-01 18:28:38 UTC
Hi Daniel, thank you very much for your time to answer my comment. That's really awesome you work with chrome browser team. You know, I have a dream to be a Programmer. I am Indonesian, i am study in Tanjungpura University Faculty of Information Technology, West Borneo. Daniel, would you mind to share with me, how tips and trick to be a good programmer, i want to share our knowledge, because Knowledge belongs to the world. Thank you :)

alirohman

Comment 5 Fedora End Of Life 2012-08-07 17:20:54 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping