Bug 788459 - SELinux is preventing /usr/libexec/kde4/kcmdatetimehelper from 'write' accesses on the None /.kde/share/config.
Summary: SELinux is preventing /usr/libexec/kde4/kcmdatetimehelper from 'write' access...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 16
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9addc1106400ab3664d9cd94b0f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-08 09:05 UTC by fernando blanco
Modified: 2012-02-13 22:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-08 09:57:34 UTC
Type: ---


Attachments (Terms of Use)

Description fernando blanco 2012-02-08 09:05:46 UTC
libreport version: 2.0.8
executable:     /usr/bin/python
hashmarkername: setroubleshoot
kernel:         3.2.3-2.fc16.i686
reason:         SELinux is preventing /usr/libexec/kde4/kcmdatetimehelper from 'write' accesses on the None /.kde/share/config.
time:           Wed 08 Feb 2012 09:51:18 AM CET

description:
:SELinux is preventing /usr/libexec/kde4/kcmdatetimehelper from 'write' accesses on the None /.kde/share/config.
:
:*****  Plugin catchall (100. confidence) suggests  ***************************
:
:If you believe that kcmdatetimehelper should be allowed write access on the config <Unknown> 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 kcmdatetimehelp /var/log/audit/audit.log | audit2allow -M mypol
:# semodule -i mypol.pp
:
:Additional Information:
:Source Context                system_u:system_r:gnomeclock_t:s0-s0:c0.c1023
:Target Context                system_u:object_r:root_t:s0
:Target Objects                /.kde/share/config [ None ]
:Source                        kcmdatetimehelp
:Source Path                   /usr/libexec/kde4/kcmdatetimehelper
:Port                          <Unknown>
:Host                          (removed)
:Source RPM Packages           kdebase-workspace-4.7.4-7.fc16.i686
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-75.fc16.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.2.3-2.fc16.i686 #1 SMP Fri Feb 3
:                              20:06:02 UTC 2012 i686 i686
:Alert Count                   6
:First Seen                    Tue 07 Feb 2012 05:14:05 PM CET
:Last Seen                     Wed 08 Feb 2012 08:57:19 AM CET
:Local ID                      97b4ddde-85cd-43d4-8b18-4fed25261f06
:
:Raw Audit Messages
:type=AVC msg=audit(1328687839.745:97): avc:  denied  { write } for  pid=2033 comm="kcmdatetimehelp" name="config" dev=sda1 ino=393219 scontext=system_u:system_r:gnomeclock_t:s0-s0:c0.c1023 tcontext=system_u:object_r:root_t:s0 tclass=dirnode=(removed) type=SYSCALL msg=audit(1328687839.745:97): arch=40000003 syscall=33 success=no exit=-13 a0=96307d8 a1=2 a2=4b6954bc a3=962b6fc items=0 ppid=1 pid=2033 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="kcmdatetimehelp" exe="/usr/libexec/kde4/kcmdatetimehelper" subj=system_u:system_r:gnomeclock_t:s0-s0:c0.c1023 key=(null)
:
:
:Hash: kcmdatetimehelp,gnomeclock_t,root_t,None,write
:
:audit2allow
:
:
:audit2allow -R
:
:

Comment 1 Miroslav Grepl 2012-02-08 09:57:34 UTC
This is a bug in KDE. You will need to execute

# semanage fcontext -a -e /usr/share/config /.config
# restorecon -R -v /.config

Comment 2 A.J. Bonnema 2012-02-12 11:36:35 UTC
Miroslav: is this bug automatically sent to KDE as well? Or does someone need to contact KDE? If yes, who? Maybe it already was reported to them?

Guus.

Comment 3 Miroslav Grepl 2012-02-13 22:36:28 UTC
Actually I have already reported many bugs on KDE with these issues. So yes, they know about that.


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