Bug 460367

Summary: Local dev mounts appear on desktops of other users
Product: [Fedora] Fedora Reporter: Warren Togami <wtogami>
Component: ltspfsAssignee: Warren Togami <wtogami>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 10   
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: 2009-07-20 19:46: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:
Bug Depends On:    
Bug Blocks: 188611    

Description Warren Togami 2008-08-27 19:45:22 UTC 
http://bugzilla.gnome.org/show_bug.cgi?id=526320#c12
http://bugzilla.gnome.org/show_bug.cgi?id=526320#c14
Despite these earlier patches against glib and ltspfs, it is still possible for local dev mounts owned by one user to appear on the desktop on other users even if they are inaccessible.  This happens in the case where all users are members of a common group and that group is their primary group.

glib W_OK instead of only R_OK might solve this problem, but the earlier idea of fsacls on /media/$username with permissions 0700 might be a better idea.  Test both ideas.
Comment 1 Warren Togami 2008-08-27 20:40:30 UTC 
http://bugzilla.gnome.org/show_bug.cgi?id=526320#c20
This makes a good point that the patches above did not actually help at all for normal GNOME.  GNOME needs to take multi-user into account.  Unfortunately while this suggested change would help normal GNOME, it wouldn't help LTSP.
Comment 2 Bug Zapper 2008-11-26 02:53:00 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Warren Togami 2009-07-20 19:46:07 UTC 
I think this isn't an issue anymore.  If it is, it should be fixed in upstream, not here.