Bug 653862 - SELinux is preventing /usr/bin/kdm "write" access to ~
Summary: SELinux is preventing /usr/bin/kdm "write" access to ~
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 14
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-16 10:18 UTC by Vytas
Modified: 2012-08-16 22:21 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 22:21:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vytas 2010-11-16 10:18:19 UTC
Summary:

SELinux is preventing /usr/bin/kdm "write" access to /home/vytautas.

Detailed Description:

SELinux denied access requested by kdm. /home/vytautas may be a mislabeled.
/home/vytautas default SELinux type is user_home_dir_t, but its current type is
admin_home_t. Changing this file back to the default type, may fix your problem.

File contexts can be assigned to a file in the following ways.

  * Files created in a directory receive the file context of the parent
    directory by default.
  * The SELinux policy might override the default label inherited from the
    parent directory by specifying a process running in context A which creates
    a file in a directory labeled B will instead create the file with label C.
    An example of this would be the dhcp client running with the dhclient_t type
    and creating a file in the directory /etc. This file would normally receive
    the etc_t type due to parental inheritance but instead the file is labeled
    with the net_conf_t type because the SELinux policy specifies this.
  * Users can change the file context on a file using tools such as chcon, or
    restorecon.

This file could have been mislabeled either by user error, or if an normally
confined application was run under the wrong domain.

However, this might also indicate a bug in SELinux because the file should not
have been labeled with this type.

If you believe this is a bug, please file a bug report against this package.

Allowing Access:

You can restore the default system context to this file by executing the
restorecon command. restorecon '/home/vytautas', if this file is a directory,
you can recursively restore using restorecon -R '/home/vytautas'.

Fix Command:

/sbin/restorecon '/home/vytautas'

Additional Information:

Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                unconfined_u:object_r:admin_home_t:s0
Target Objects                /home/vytautas [ dir ]
Source                        kdm
Source Path                   /usr/bin/kdm
Port                          <Unknown>
Host                          aspire.one
Source RPM Packages           kdm-4.5.2-3.fc14
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.7-7.fc14
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Plugin Name                   restorecon
Host Name                     aspire.one
Platform                      Linux aspire.one 2.6.35.6-48.fc14.i686 #1 SMP Fri
                              Oct 22 15:34:36 UTC 2010 i686 i686
Alert Count                   27
First Seen                    Fri 05 Nov 2010 10:39:54 PM EET
Last Seen                     Tue 16 Nov 2010 12:16:58 PM EET
Local ID                      764479be-31be-4d93-997f-826fb29b5999
Line Numbers                  

Raw Audit Messages            

node=aspire.one type=AVC msg=audit(1289902618.221:92): avc:  denied  { write } for  pid=4440 comm="kdm" name="vytautas" dev=dm-0 ino=393745 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:admin_home_t:s0 tclass=dir

node=aspire.one type=SYSCALL msg=audit(1289902618.221:92): arch=40000003 syscall=10 success=no exit=-13 a0=9d6e548 a1=0 a2=9d6e548 a3=1f4 items=0 ppid=4416 pid=4440 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=6 comm="kdm" exe="/usr/bin/kdm" subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null)

Comment 1 Bill Nottingham 2010-11-16 16:01:25 UTC

*** This bug has been marked as a duplicate of bug 649227 ***

Comment 2 Bill Nottingham 2010-11-16 16:02:13 UTC
Whoops, sorry about that. Reopening.

Comment 3 Fedora End Of Life 2012-08-16 22:21:12 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. 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 '14' 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 14 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


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