Bug 118853
Summary: | s-c-u doesn't properly label attributes on created users | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | G.Wolfe Woodbury <redwolfe> |
Component: | system-config-users | Assignee: | Brent Fox <bfox> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | aleksey |
Target Milestone: | --- | Keywords: | Security, SELinux |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:02:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 114961 |
Description
G.Wolfe Woodbury
2004-03-21 17:49:35 UTC
Can you try creating a user with luseradd and then try to log in with that user. Does the problem still occur with that user? created a new user with luseradd, there were still problems logging in. The user home directory was messed up in its context and GDM login failed severly, here is the ssh trace: [ggw@baboushka ggw]$ ssh sfw sfw's password: /usr/X11R6/bin/xauth: timeout in locking authority file /home/sfw/.Xauthority -bash: /home/sfw/.bash_profile: Permission denied -bash-2.05b$ ls -lZa drwx------+ sfw sfw root:object_r:home_root_t . drwxr-xr-x root root system_u:object_r:home_root_t .. ?--------- root root (null) .bash_logout ?--------- root root (null) .bash_profile ?--------- root root (null) .bashrc ?--------- root root (null) .emacs ?--------- root root (null) .gtkrc drwxr-xr-x sfw sfw root:object_r:home_root_t .kde drwxr-xr-x sfw sfw root:object_r:home_root_t .xemacs ?--------- root root (null) .zshrc -bash-2.05b$ *** This bug has been marked as a duplicate of 118061 *** Bug 118061 is not public :-( P.S. See also bug 118571. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |