Bug 3271
Summary: | gdm-1.1.0-35 silently fails if home directory is 777 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | nelson |
Component: | gdm | Assignee: | Elliot Lee <sopwith> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | CC: | mkp |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-10-29 14:38:07 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: |
Description
nelson
1999-06-04 16:59:41 UTC
This is listed as Gnome bug report #1393 I have verified this to be true on a test lab machine with a stock 6.0 intall. I created a sample user account. chmod 777 that users home directory. Then using gdm attempted to login as the sample user with out success. It would come back to the gdm login screen. I then chmod 755 the home directory and then was able to successfully login to the gnome desktop. This might just be a good security measure - with xauth style security, a world-writeable home directory is a really bad idea. If this is correct behaviour, then the "fix" should be to make sure the user understands why they weren't allowed to log in. Some sort of visible error message... Assign to mkj for now. Try getting the gdm-2.0beta2-13 from RHL 6.1 |