Wine being targeted for adware

[Nicholas LaRoche]

Gert van den Berg wrote:
> On Thu, Jan 15, 2009 at 7:50 PM, Austin English <austinenglish at gmail.com> wrote:
>> Of course, Wine is open source, so if someone wants to edit it for
>> that purpose, by all means, do so. I'm not sure that Wine _should_ do
>> so though, at least, not now. Networking on a per app basis I can see
>> an argument for, since Windows Firewall is now included and provides
>> such a feature.
> 
> Can't SELinux or something similar disable network access per-application?
> 
> I would think that this kind of functionality should be provided by
> the OS, not by Wine. (Having control over what can / can't get to the
> network can be real handy for purposes such as server-hardening.)
> (Solaris Trusted Extensions seem to provide this kind of
> functionality...)
> 
> Wine should probably at least provide APIs that can be used by
> anti-malware applications... (I'm not sure about recent applications,
> but, IIRC, older ones under Windows 9x used to use drivers for
> on-access scanning which is not currently supported in Wine)
> 
> Gert
> 

It probably does disable network access, but you would have to play 
around with policies on the fly to accomplish this. If a patch were made 
to disable it within wine then you could turn it on and off with a 
command line switch. One takes more time than the other, but both should 
be valid.

-Nick