griffinp at MIT.EDU
Tue Jun 3 11:11:06 CDT 2003
Having returned from vacation, I'm back to work on winecfg.
In order to do drive autodetection from within the win32 API, I've been
using the /etc/fstab file. Of course, this implies that winecfg (a
win32 program) needs access to the / directory. Talk about mixing your
Anyway, winecfg needs to fopen( "/etc/fstab",...) so Wine needs to
provide access to /. As things currently stand, anyway. My impression
is that we'll have to rely on Unix security measures to prevent programs
from over-running stuff they shouldn't, which is what we're currently
doing anyway. That's why you shouldn't run wine as root.
My impression is that / access is necessary for an effective winecfg
and desirable in many other cases, as well (opening arbitrary Linux
files in Windows programs). Now, if we want winecfg to create separate
users for running Wine with limited access or some such, it could be
discussed, but it seems like far too much complexity to worry about
Summary: "/" access in Wine is good.
On Tue, 2003-06-03 at 11:27, puoti wrote:
> >The only thing that the / access gave Klez was (potentially) more files
> >to harvest email addresses from. As far as drive access, the author was
> >much more concerned about having write access to the home directory. If
> >anybody is interested, here is the article:
> >BTW, I do not object to having access to the root drive, but what does
> >a *windows* program really gain from that? Viewing system config files
> >in notepad? ;-> Is it just a solution in search of a problem?
> That's the article I read, I don't think there's any reason for having / in the
> config file, if klez used it, other viruses may use / to infect and spread via
> linux boxes in the future.
More information about the wine-devel