Bug 237324 - LSPP: genhomedircon does not pick up default user types correctly
LSPP: genhomedircon does not pick up default user types correctly
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: policycoreutils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2007-04-20 15:57 EDT by Daniel Walsh
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHBA-2007-0543
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 13:04:10 EST
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 Daniel Walsh 2007-04-20 15:57:01 EDT
Description of problem:
If I change the default user type of the default user, genhomedircon continues
to set the labeling to user_u.

In MLS policy, I could set default user to be staff_u

Steps to cause the problem:
semanage login -m -s staff_u __default__
grep /home /etc/selinux/mls/contexts/files/file_context.homedirs

Should be staff_u and staff_* instead of user_u and user_*

For defaults
Comment 1 Daniel Walsh 2007-04-20 16:19:50 EDT
Fixed in policycoreutils-1.33.12-8
Comment 2 RHEL Product and Program Management 2007-04-20 16:24:00 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 4 Steve Grubb 2007-04-24 13:07:53 EDT
This bug is reported to be fixed, removing from LSPP query.
Comment 8 errata-xmlrpc 2007-11-07 13:04:10 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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