Bug 455774 - genhomedircon does not filter out conflicts
genhomedircon does not filter out conflicts
Product: Fedora
Classification: Fedora
Component: policycoreutils (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Walsh
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-17 13:25 EDT by Jeff Moyer
Modified: 2008-09-17 14:34 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-09-17 14:34:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeff Moyer 2008-07-17 13:25:01 EDT
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
<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
<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):
Comment 1 Daniel Walsh 2008-07-17 14:54:55 EDT
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.