On Thu, Oct 24, 2002 at 08:08:49AM -0700, Dustin Navea wrote: > > > or what if someone just changes the > > > owner/group on the file (like a word doc), and > > then > > > tries to run it with wine, what happens then? > > > > Unless wine has some suid capabilities (which it > > shouldn't) > > this has no impact - wine runs in the account of the > > user who opens the > > file (runs word).
> I was actually thinking more from a read the file > standpoint, i.e if in the future wine runs as a > service with its own account, would wine be able to > read the file after someone changed the file's owner > from wine to, say user speeddy, or would it just say > access denied and not let you read the file, therefore > making you have to redo the permissions or make it > owned by wine again. Just as wine should not be run as root, file i/o in wine should NEVER be done in a security context other than that of the user running the Windows app. Anything that would cause user data files to be written out under a different uid is broken. Steve Langasek postmodern programmer
