Bug 683356 - SELinux is preventing /usr/libexec/mission-control-5 from 'read' accesses on the file .mc_connections.
Summary: SELinux is preventing /usr/libexec/mission-control-5 from 'read' accesses on ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 15
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:21d42972c61...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-09 09:00 UTC by Michal Schmidt
Modified: 2011-03-31 12:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-09 11:14:16 UTC
Type: ---


Attachments (Terms of Use)

Description Michal Schmidt 2011-03-09 09:00:58 UTC
SELinux is preventing /usr/libexec/mission-control-5 from 'read' accesses on the file .mc_connections.

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

If you believe that mission-control-5 should be allowed read access on the .mc_connections 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 mission-control /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:telepathy_mission_contro
                              l_t:s0-s0:c0.c1023
Target Context                unconfined_u:object_r:user_home_t:s0
Target Objects                .mc_connections [ file ]
Source                        mission-control
Source Path                   /usr/libexec/mission-control-5
Port                          <Neznámé>
Host                          (removed)
Source RPM Packages           telepathy-mission-control-5.7.2-2.fc15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.16-1.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 2.6.38-0.rc8.git0.1.fc15.x86_64 #1 SMP
                              Tue Mar 8 08:22:15 UTC 2011 x86_64 x86_64
Alert Count                   2
First Seen                    St 9. březen 2011, 09:55:46 CET
Last Seen                     St 9. březen 2011, 09:59:36 CET
Local ID                      f3f44d24-6fe1-4b07-abf9-54347c046658

Raw Audit Messages
type=AVC msg=audit(1299661176.185:221): avc:  denied  { read } for  pid=4043 comm="mission-control" name=".mc_connections" dev=dm-1 ino=262990 scontext=unconfined_u:unconfined_r:telepathy_mission_control_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file


type=AVC msg=audit(1299661176.185:221): avc:  denied  { open } for  pid=4043 comm="mission-control" name=".mc_connections" dev=dm-1 ino=262990 scontext=unconfined_u:unconfined_r:telepathy_mission_control_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file


type=SYSCALL msg=audit(1299661176.185:221): arch=x86_64 syscall=open success=yes exit=ENOEXEC a0=220b620 a1=0 a2=0 a3=7463656e6e6f635f items=0 ppid=4042 pid=4043 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=4 comm=mission-control exe=/usr/libexec/mission-control-5 subj=unconfined_u:unconfined_r:telepathy_mission_control_t:s0-s0:c0.c1023 key=(null)

Hash: mission-control,telepathy_mission_control_t,user_home_t,file,read

audit2allow

#============= telepathy_mission_control_t ==============
allow telepathy_mission_control_t user_home_t:file { read open };

audit2allow -R

#============= telepathy_mission_control_t ==============
allow telepathy_mission_control_t user_home_t:file { read open };

Comment 1 Michal Schmidt 2011-03-09 09:07:23 UTC
I had defined one Jabber account in Empathy.
This denial appeared after logging in to Gnome.
The target file is $HOME/.cache/.mc_connections

Comment 2 Miroslav Grepl 2011-03-09 11:14:16 UTC
restorecon -R -v ~/

will fix it.


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