Comodo Firewall refuses to re-recognize WoW Launcher

[Guest]

[madanasta]

As ivanstehlik pointed out above, what the launcher does is create and spawn a *copy* of itself in a new directory it creates (and names appending a random number each time) inside the "Documents and Settings | <username> | Local Settings | Temp" directory. So, the problem has nothing to do with parent checking, digital signatures, etc. It has to do with the fact that that launcher copy is in fact a *new* program, one that Comodo knows *nothing* about. Hence, it very wisely asks you. Atm I don't see anything that can be done about it.

[madanasta]

On the other hand, post #88 on http://forums.worldofwarcraft.com/thread.html?topicId=14498459986&sid=1&pageNo=5 seems to "solve" the "problem", although, as correctly stated later, making the firewall stop shouting about the new application (by giving permissions to actually everything in the new folder) is a serious security risk. And it sure overrides Blizzard's intention to *make* your firewall ask you each and every time you run the launcher.

[papatrexas]

Greetings,

I had the same problem till i added as a safe application this
C:\ProgramData\Battle.net\Agent\Agent.1544\agent.exe
the only thing is that each time a new agent comes up you will have to update the list at your firewall
for instance after a week or so the path will be
C:\ProgramData\Battle.net\Agent\Agent.1566\agent.exe
or what ever... so far this is the only thing working for me. ofc you can go with the zone thing i saw someone posting upstairs
regards,

Papatrexas

[Tags:]