Re: Add root drive mapping to default config file
Adding / to the default config file is a very bad idea, I remember reading somewhere on the net that once someone opened his mail with kmail, KDE started the attachment (A windows virus) with wine, and the virus sent itself to other users on the net. I don't remembered the details, but I do remember that the virus could get out the the net because of that / being in the wine config. So having / in the default config file is a very very bad idea, because these problems could happen again in the future. A solution to get people to have a good configuration, would be to have winsetuptk as a "official" winehq utility, and recommending people to use it to set up wine, but unfortunately winsetuptk puts / in the config file, but that can be changed. It also maps all the removable drives. BTW I've added binaries and source of winesetuptk to the wine sourceforge page, the license is gpl.
I don't remembered the details, but I do remember that the virus could get out the the net because of that / being in the wine config.
How did that work? I can't think of anything whatsoever that a win32 program under emulation could do with ro access to / - it can't run ELF apps, it can't write, it can't understand the format of the config files even!
So having / in the default config file is a very very bad idea, because these problems could happen again in the future.
The solution is for people not to use mail apps that implicitly trust any local software which gives them email, not to annoy and frustrate users of Wine for no obvious reason. As I've already said, I'd need strong proof that having / mapped allowed viruses to spread more easily before I'd accept this argument.
BTW I've added binaries and source of winesetuptk to the wine sourceforge page, the license is gpl.
Cool :) -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center
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: http://articles.linuxguru.net/view/198 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? -- Jeff Smith --- puoti <puoti(a)inwind.it> wrote:
Adding / to the default config file is a very bad idea, I remember reading somewhere on the net that once someone opened his mail with kmail, KDE started the attachment (A windows virus) with wine, and the virus sent itself to other users on the net. I don't remembered the details, but I do remember that the virus could get out the the net because of that / being in the wine config. So having / in the default config file is a very very bad idea, because these problems could happen again in the future. A solution to get people to have a good configuration, would be to have winsetuptk as a "official" winehq utility, and recommending people to use it to set up wine, but unfortunately winsetuptk puts / in the config file, but that can be changed. It also maps all the removable drives. BTW I've added binaries and source of winesetuptk to the wine sourceforge page, the license is gpl.
__________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com
On Tue, 3 Jun 2003, Jeff Smith 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: : : http://articles.linuxguru.net/view/198 I feel like having a seafood grillout today, even though I'm vegetarian. Today's special is... RED HERRING... with a FUD buffet on the side. If arbitrary code is being executed on *any* platform, there's no way we can help the poor sap. This is not restricted to Windows. A person can run a trojan horse on any system. : a *windows* program really gain from that? Viewing system config files : in notepad? ;-> Is it just a solution in search of a problem? There's plenty of application. To put it in short, convenience to be able to use a Windows program on an arbitrary file. (I put in my / mapping when I needed to run MS Media Sprayer on a group of files for an obscure Windows-only codec, and didn't want either to move the files around or create a specialized mapping for just that file group.) -- -- Todd Vierling <tv(a)pobox.com>
participants (4)
-
Jeff Smith -
Mike Hearn -
puoti -
Todd Vierling