Any resolution on KB 46158: Firewalls not able to remember virtualized programs in exception list?
I've already subscribed this article, but was wondering if this has been fixed:
article 46158: KNOWN ISSUE: Firewall blocking virtualized programs even though program listed in firewall''s exception list.
https://kb.altiris.com/display/1n/kb/article.asp?a...
Currently, I'm running Comodo Firewall and its associated "Defense" HIPS-like system and find that no matter what kind of exclusions I put in the SWV ProgramIgnoreList registry setting, it (Comodo) can't seem to exclude SWV-layer programs that trigger the protection prompts. This problem is very similar to the article above as I have also observed previously that I can't get Windows Firewall to allow SWV-layer programs that trigger it.
The problem seems to be how SWV-layer programs present its path to the firewalls (In Comodo and Windows Firewall). The firewalls seems to see the true exe paths when offering to save it for exclusion. However, later on when the program runs, it triggers the prompts again, maybe because it is triggering it using the virtual path.
I hope that this problem can be resolved soon if it hasn't. Being able to run a firewall along with SWV should be an expected use-case scenario.
Comments
yes and no. There are ways to
yes and no.
There are ways to work around it and it just depends on your software, but it's not something we've done within the product. I think I've worked around this on comodo before.
The easiest way is to see if your firewall has a program exclude list and add our driver to that.
The next way to to add to the approved program list both the virtualized path (c:\program files\firefox\firefox.exe) and the redirect path (C:\fslrdr\#\[_B_]PROGRAMFILES[_E_]\Firefox\firefox.exe).
If a forum post solves your problem please flag is as the solution
Do those methods work for Windows Firewall?
Dear Jordan,
Thank you for replying with a possible solution. Unfortunately, for Comodo, and also Windows Firewall, there's no way to add the driver to the exclude list. I have tried the 2nd method as well, by adding both the virtualized path and the redirect path to the approved program list, but it also didn't work. For now, it would be great to be able to run SWV with at least some kind of firewall, even if it is the Windows built-in one. Are there other methods that other members are using to have SWV and firewalls co-exist ? Thanks in advance.
I've never had an issue with
I've never had an issue with Windows firewall, when on default settings, and SWV.
If a forum post solves your problem please flag is as the solution
Test on Win XP SP3 fails
Dear Jordan,
To assist in troubleshooting and eliminate other variables, I created a test case using yet another virtualization method. I had Win XP SP3 installed into a Virtual Machine created under VirtualBox (with bridged networking). After that, I installed SWV into this VM and tried to simulate my use case. For simplicity, I used an open-source webserver file-sharing application called HFS (www.rejetto.com/hfs). This program is so small that it doesn't even come with an installer. So to create a new SWV layer, i used SWV to start-up cmd.exe and had it copy the .exe into C:\program files.
Would you like to reply?
Login or Register to post your comment.