Bug 755324 - SELinux is preventing /usr/sbin/lxdm-binary from 'unlink' accesses on the archivo .Xauthority.
Summary: SELinux is preventing /usr/sbin/lxdm-binary from 'unlink' accesses on the arc...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:aa9f8725e365d886d0d8394ff5d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-20 16:53 UTC by Juan
Modified: 2011-11-21 14:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-21 12:11:14 UTC
Type: ---


Attachments (Terms of Use)

Description Juan 2011-11-20 16:53:43 UTC
libreport version: 2.0.6
executable:     /usr/bin/python
hashmarkername: setroubleshoot
kernel:         3.1.1-2.local.fc16.x86_64
reason:         SELinux is preventing /usr/sbin/lxdm-binary from 'unlink' accesses on the archivo .Xauthority.
time:           Sun Nov 20 17:52:05 2011

description:
:SELinux is preventing /usr/sbin/lxdm-binary from 'unlink' accesses on the archivo .Xauthority.
:
:*****  Plugin catchall (100. confidence) suggests  ***************************
:
:If cree que de manera predeterminada, lxdm-binary debería permitir acceso unlink sobre  .Xauthority file.     
:Then debería reportar esto como un error.
:Puede generar un módulo de política local para permitir este acceso.
:Do
:permita el acceso momentáneamente executando:
:# grep lxdm-binary /var/log/audit/audit.log | audit2allow -M mypol
:# semodule -i mypol.pp
:
:Additional Information:
:Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
:Target Context                unconfined_u:object_r:home_root_t:s0
:Target Objects                .Xauthority [ file ]
:Source                        lxdm-binary
:Source Path                   /usr/sbin/lxdm-binary
:Port                          <Desconocido>
:Host                          (removed)
:Source RPM Packages           lxdm-0.3.0-4.fc16
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-55.fc16
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.1.1-2.local.fc16.x86_64
:                              #1 SMP PREEMPT Sun Nov 20 00:19:19 CET 2011 x86_64
:                              x86_64
:Alert Count                   1
:First Seen                    dom 20 nov 2011 17:47:11 CET
:Last Seen                     dom 20 nov 2011 17:47:11 CET
:Local ID                      b903270d-fafb-47d1-be21-8f06c21ac3eb
:
:Raw Audit Messages
:type=AVC msg=audit(1321807631.247:47): avc:  denied  { unlink } for  pid=1063 comm="lxdm-binary" name=".Xauthority" dev=dm-1 ino=525739 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:home_root_t:s0 tclass=file
:
:
:type=SYSCALL msg=audit(1321807631.247:47): arch=x86_64 syscall=unlink success=no exit=EACCES a0=6e3e70 a1=5 a2=0 a3=0 items=0 ppid=932 pid=1063 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=(none) ses=1 comm=lxdm-binary exe=/usr/sbin/lxdm-binary subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null)
:
:Hash: lxdm-binary,xdm_t,home_root_t,file,unlink
:
:audit2allow
:
:#============= xdm_t ==============
:allow xdm_t home_root_t:file unlink;
:
:audit2allow -R
:
:#============= xdm_t ==============
:allow xdm_t home_root_t:file unlink;
:

Comment 1 Miroslav Grepl 2011-11-21 12:11:14 UTC
Looks like your HOMEDIR is mislabeled

# restorecon -R -v /home

should fix the issue. Is this a fresh install with updates?

Comment 2 Juan 2011-11-21 14:30:02 UTC
Well, yes, I installed the LXDM spin from a live image in a usb pendrive and updated everything.

I had some strange issue that rendered the window manager unusable and my only workaround was to delete my home dir and let it be created again the next login (I had checked the option that home dirs are automatically created at login time if they don't exist yet).

I really don't rememeber if that was before or after this bug, but if I deleted my home dir, it looks like a logical cause for the new one to be mislabeled.... if it isn't a bug that when recreating a home dir it isn't automatically properly labeled.


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