Tero Tamminen valeo@phreaker.net writes:
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?
Actually ZoneAlarm checks MD5 or some other checksum, but it can also be configured so, that it doesn't care about those.
Fine, so far. This is absolutely needed, no way around.
There is option where I can specify that "Athenticate program by full path name only"... name says all
I see, thanks for the info.
Zonealarm only sees that, these programs are launcehd from different directory,
I will put in a "try this first" directory name, and fall back to "random" names if creating that fails.
they have different checksum,
We can't help this, but it shouldn't pose a problem, right?
wine-test-whatever executable has different name (because date is part of the name),
We can change this, too.
At least to my knowledge ZoneAlarm can't be configured with wildcards, so that it would check only part of the executable name.
What a shame. We'll have to go the "hard" way then.
But anyway, it is okay to me if you don't want to program temp directories not to be random, I just have to disable winrash and thus winetests from my win2k3 server.
What would be a shame again, we aren't particularly overwhelmed with Win2k3 testers. Hope we can sort it out. In the meantime just disable winrash if it's too disturbing, I'll drop you a note once the necessary changes are in place.