Bug 455774 - genhomedircon does not filter out conflicts
Summary: genhomedircon does not filter out conflicts
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: policycoreutils
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-17 17:25 UTC by Jeff Moyer
Modified: 2008-09-17 18:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-17 18:34:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jeff Moyer 2008-07-17 17:25:01 UTC
Description of problem:
I had a passwd entry that used /var/crash as its home directory, and a login
shell of /bin/bash.  I ended up getting a lot of message like this:

/etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications
for /var/lost\+found/.*.

<dwalsh>genhomedircon labels the parent directory home_root_t and the child
user_home_dir_t.
<dwalsh> So /var -> home_root_t. crash user_home_dir_t
<dwalsh> Confined domains are not allowed in users homedir.
<dwalsh> useradd -d /var/dwalsh1 dwalsh1
<dwalsh> genhomedircon 
<dwalsh> matchpathcon /var/dwalsh1
<dwalsh> /etc/selinux/targeted/contexts/files/file_contexts: Multiple same
specifications for /var/lost\+found/.*.
<dwalsh> /etc/selinux/targeted/contexts/files/file_contexts: Multiple different
specifications for /var  (system_u:object_r:home_root_t:s0 and
system_u:object_r:var_t:s0).
<dwalsh> /etc/selinux/targeted/contexts/files/file_contexts: Multiple same
specifications for /var/\.journal.
<dwalsh> /etc/selinux/targeted/contexts/files/file_contexts: Multiple same
specifications for /var/lost\+found.
<dwalsh> /var/dwalsh1 system_u:object_r:user_home_dir_t:s0
<dwalsh> The genhomedircon should have complained and not added the entries.

Version-Release number of selected component (if applicable):
policycoreutils-2.0.49-10.fc9.x86_64

Comment 1 Daniel Walsh 2008-07-17 18:54:55 UTC
Fixed in libsemanage-2.0.25-3.fc9


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