Wine test suite (or winrash, don't know which one) - possible way to improve for some persons (with some antivirus or firewall software running)

[Ferenc Wagner]

Vincent Béron <vberon at mecano.gme.usherb.ca> writes:

> Le ven 10/12/2004 à 07:26, Francois Gouget a écrit :
>> On Fri, 10 Dec 2004, Ferenc Wagner wrote:
>> 
>> > Francois Gouget <fgouget at free.fr> writes:
>> [...]
>> >> I've had some dealings with ZoneAlarm and I thought it
>> >> also saved an md5 checksum of the executable.
>> >
>> > Yes, please clear this issue up for me!  After some
>> > discussion on IRC I almost started changing the code :)
>> > Also, can't ZoneAlarm use wildcards perhaps?  I couldn't
>> > find out from the webpage...
>> 
>> Well... this is not on a machine I have access to. What you could do is 
>> take an old verion of one of Wine's conformance tests (wininet should 
>> do) that accesses the net, run it and configure ZoneAlarm to let it 
>> through, then download a newer version and put it in exactly the same 
>> place and try again. I strongly suspect that ZoneAlarm is going to ask 
>> you again.
>
> Newer ZoneAlarm don't only warn on accessing the network but also on
> launching unknown applications. So merely launching winetests (which
> launches the other .exe itself via CreateProcess) will get the question
> to let it run or not asked, in part because the path to the test changes
> with each release (the temp dir name is random).

Yes.  But will sticking to a fixed directory name (and
possibly file name) help, or does ZoneAlarm check eg. MD5
sums to thwart any countermeasure from our side?  Anyway, I
have the feeling that this should be solved by configuring
ZoneAlarm instead of throwing in kludges.  Don't you know if
it's possible to disable this warning for an application or
a directory?
-- 
Feri.