Tracker item #3537235, was opened at 2012-06-22 11:27
Message generated for change (Tracker Item Submitted) made by mroi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3537235&group_id=204462

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Michael Roitzsch (mroi)
Assigned to: Nobody/Anonymous (nobody)
Summary: uid and gid mount options should be checked for chown()

Initial Comment:
When mounting vmhgfs with the uid or gid mount options, these options should be 
considered when a chown() system call is being executed to change the owner or 
group. When the caller is running with the same uid/gid as in the mount option 
and tries to chown() a file to that same uid/gid, the operation should be 
treated as a noop and should not return an error. The current code paths check, 
whether the change would be allowed on the host, which they may not. However, 
since no actual change is being requested (uid/gid is "changed" to the current 
value), the error is unexpected by the caller.

I need this change to use vmhgfs as a user home directory. Some per-user agents 
(I noticed with pulse audio) want to be really safe in creating a secure 
directory in the user’s $HOME: They create a new directory and then chown() it 
to the uid/gid of the user. With vmhgfs underneath, this will result in an 
error, causing the agent to quit. The attached patch fixes the issue for me.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3537235&group_id=204462

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
open-vm-tools-devel mailing list
open-vm-tools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel

Reply via email to