Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: SamHui on February 24, 2012, 09:43:39 AM
-
Hi, is anyone experiencing this bug with Comodo Firewall and Avast 7? With Avast7, Comodo firewall does not block your internet traffic unless you choose to block all traffic. For example, if I told Comodo to block Firefox the logs would indicate that the Firefox attempt to access the internet was blocked, however I could freely surf the internet and visit many different websites even when Comodo firewall states that the actions had been blocked. If I were to disable the webshield then Firefox would not be able to access the internet as intended, but with Webshield on, regardless of what I tell Comodo firewall to do, it does not block the outgoing and incoming traffic. This also happens to other programs like Avast itself, IE, or any programs that requires internet access. Comodo would state that it was blocked, but the program actually still did have access to the internet. This happened only with Avast7, it was fine with Avast6. Thanks.
-
Just 1 quick item to add, in the Comodo logs, the blocked events would have all zeros in the source ip, but it usually has your ip as the source ip.
-
Try to delete all Avast!-related rules in Comodo, then let it ask for access again.
-
Hi, I did that and even re-installed Comodo. Seems like the firewall in Comodo is not working properly when Avast7 webshield is on. If it's off, the selective blocking works. At least right now, it's either block all or nothing for the Comodo firewall when the Avast7 webshield is on. Thanks.
-
Hi,
I would like to confirm that I'm seeing the exact same behaviour.
Comodo FW has essentially been made irrelevant.
I do believe this is a Comodo issue and not Avast.
EDIT: I started a topic in F/W help in the Comodo Forum - https://forums.comodo.com/firewall-help-cis/comodo-does-not-work-with-avast-7-t82323.0.html
My System Specs are: Win7 home premium | core I3 | 4GB memory
Avast Free | Comodo F/W only
-
I don't have that problem in Windows XP with Comodo.
I don't use Comodo's Defense+ and Sandbox.
-
I can't check that as I don't use Comodo. But I have used it in the past and there was no such problem. May be you guys try to restrict the web shield scope to browsers only and not the whole system (in settings), and see if that changes anything...
... not sure, sounds rather like the web shield in V7 might be denying access to any other monitoring app
-
@ SamHui and Hellion
My Comodo firewall working OK here. Did you check if you still have your exclusions for each other progs in place after the upgrade ?
-
Hi Iroc,
My Comodo firewall working OK here. Did you check if you still have your exclusions for each other progs in place after the upgrade ?
The only exclusions I have are in Avast. Excluded are cmdagent memory process and the Comodo install folder.
Have you tested properly?
Clear your Comodo rules and block your browser and see if you can access webpages.
-
The only exclusions I have are in Avast. Excluded are cmdagent memory process and the Comodo install folder.
Open Avast > Real Time Shields > File System > Expert Settings > Exclusions. Add:
C:\Program Files\COMODO\*
C:\Documents and Settings\All Users\Application data\Comodo\*
Also in:
Real Time Shields > Behavior Shield > Expert Settings > Trusted processes. Add:
C:\Program files\COMODO\COMODO Internet Security\cfpconfg.exe
C:\Program files\COMODO\COMODO Internet Security\cfp.exe
C:\Program files\COMODO\COMODO Internet Security\cmdagent.exe
Now in Comodo:
Open Comodo > Defence + > Defence+ Settings > Execution Control Settings > Exclutions Add > Browse > Add all you can find of Avast!
Have you tested properly?
Clear your Comodo rules and block your browser and see if you can access webpages.
Cleared all my Avast! rules in Comodo Firewall and D+. Rebooted. Comodo recreated rules for Avast ( Default ). Blocked FF and tried to browse with it. FF unable to connect, again. See my screenshots.
-
Double post deleted ???
-
Triple post deleted :o ???
-
Open Avast > Real Time Shields > File System > Expert Settings > Exclusions. Add:
C:\Program Files\COMODO\*
C:\Documents and Settings\All Users\Application data\Comodo\*
Also in:
Real Time Shields > Behavior Shield > Expert Settings > Trusted processes. Add:
C:\Program files\COMODO\COMODO Internet Security\cfpconfg.exe
C:\Program files\COMODO\COMODO Internet Security\cfp.exe
C:\Program files\COMODO\COMODO Internet Security\cmdagent.exe
Added and I think it worked for me ;)
Sorry, I have problems again :'(
I use the old Comodo 2.4 in Win2k and I don't have cfpconfg.exe: added the others.
Thank you.
-
c64
Sorry to hear it did not work. You can follow a similar discussion in Comodo forums:
https://forums.comodo.com/firewall-help-cis/comodo-does-not-work-with-avast-7-t82323.0.html;msg587784#msg587784
Someone may come with a correct answer.
Regards.
-
I have the same problem, with webshield enabled the comodo firewall don't work. When the webshield stopped, it works properly.
Win 7 64 bit
-
Not having any problems with my comodo firewall
-
I'm running Win 7 64 bit and it happened to me too: Comodo was saying it was blocking what I told it to, but Avast was letting it right through (unless I turned Web Shield off). I've since reinstalled V6 and the firewall seems to be working as it should once again. Looks like it's only happening on Win 7 and Win 2000 machines.
-
If you enable "Scan traffic from well-known browser processes only" in Web Shield Expert Settings, this behavior should be changed.
This option is disabled by default, and with default settings all traffic via port 80 and some are redirected to AvastSvc.exe and firewall cannot stop them.
If you want to use firewall effectively, you have to enable this option.
-
I already tried the various options in the webshield settings to no avail. Currently the only way I can see that enables Comodo firewall to work is by disabling webshield. It does look like that all the traffic is being transferred through AvastSvc.exe. If I block Avastsvc.exe through Comodo Firewall, then all the programs that requires internet access like firefox, internet explorer, mbam, etc. would not work. The programs won't even ask for permission, it just straight out does not connect when Avastsvc.exe is blocked in Comodo. Using Windows 7 32bit. Thanks.
-
"Scan traffic from well-known browser processes only" works for me too, comodo block internet access again (Win 7 64 bit)
-
Hi Iroc,
My Comodo firewall working OK here. Did you check if you still have your exclusions for each other progs in place after the upgrade ?
The only exclusions I have are in Avast. Excluded are cmdagent memory process and the Comodo install folder.
Have you tested properly?
Clear your Comodo rules and block your browser and see if you can access webpages.
Glad I came across this topic. No idea whatsoever.
As a test, I changed the rules for FF from Web Browser to Blocked Application. FF would not connect. Changed back again to Web Browser, connectivity back. Could this bug be OS specific? Maybe just Win7? Does anyone see a pattern here?
-
If you enable "Scan traffic from well-known browser processes only" in Web Shield Expert Settings, this behavior should be changed.
This option is disabled by default, and with default settings all traffic via port 80 and some are redirected to AvastSvc.exe and firewall cannot stop them.
If you want to use firewall effectively, you have to enable this option.
Had the same problem with webshield with the Windows 7 firewall and this is the fix.
-
Hi All,
I would just like to report back on my findings...
I added all Exclusions mentioned by Iroc and I enabled the "scan well known browser processes only" and my situation has not changed.
Firefox blocked, but I can browse freely.
Windows 7 Home Premium x64 | Comodo latest | Avast latest
-
Hi All,
I would just like to report back on my findings...
I added all Exclusions mentioned by Iroc and I enabled the "scan well known browser processes only" and my situation has not changed.
Firefox blocked, but I can browse freely.
Windows 7 Home Premium x64 | Comodo latest | Avast latest
Firefox is "well-known browser" so avast redirects Firefox's connection even with "scan well known browser processes only" enabled.
I remember there is an option called "Excluded processes" in Web Shield settings, so if you exclude firefox.exe then you could block Firefox by Comodo. Of course, web shield doesn't work with this settings.
-
Hi NON,
I want to be able to control my applications, but also receive maximum protection from Avast.
EDIT: Another Comodo thread where Avast 7 has rendered a user's FW useless - https://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.0.html
-
Hi all,
Sorry for double post, but no one has responded in 24 H.
This is a really big security issue!
-
Set Firefos's proxy settings to localhost:12080, then Comodo can block firefox connection.
localhost:12080 means Web Shield, so Web Shield can scan Firefox traffics.
I would say this is how Web Shield works, so it can't be helped if you want further control.
At least I don't know the way to do it.
And I don't see any reason to manually allow/block Firefox connections...
-
Just thought I'd let you know the problem's not confined to Comodo firewall, it also happens with the Windows 7 firewall and it's not just about firefox. You can easily try this.
Install Avast 7 and make sure everything works correctly
Change the properties of the Windows 7 firewall profiles, so that 'Outbound connections that do not match a rule are blocked'
Try to make a connection with a browser - it should fail because there's no rule to allow the connection.
Now add a rule to allow AvastSvc.exe to make outbound connections.
Reopen you browser and try to make a connection. This time it will succeed, even though it still doesn't have a rule of it's own.
Now open any application that uses a direct connection over TCP port 80 for updates and try to update. It will also succeed, again without an explicit rule
These connections work because they being routed through the Avast proxy and it shouldn't be happening this way, it's making a mockery of the firewall(s). There again, the firewall(s) should be able to block these connections...
Edit: If an explicit block rule, for the browser, is added to the firewall, connections can still be made. This is in a firewall where block rules take precedence over allow rules.
If anyone has tried any other firewalls it would be good to know if they also allow these connections.
-
Hi Dogstar,
Please view this post in the Comodo forums.
Radaghast did some tests with Firewalls - https://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.15.html
-
Hi Dogstar,
Please view this post in the Comodo forums.
Radaghast did some tests with Firewalls - https://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.15.html
Thanks, I'll take a look.
-
Hi,
I really wish someone on the Avast team would post on here so we know something is being done.
I have a feeling this Issue with Comodo is being ignored.
-
I really wish someone on the Avast team would post on here so we know something is being done.
+1
Eventhough it seems a Comodo bug and it is not seen in Windows XP, there are a lot of W7 users running Avast! free ( no firewall ) and Comodo firewall who might not be aware of this.
Radaghast, a Comodo's hero, already file a bug report after he ran test with several firewalls.
https://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.0.html;msg588619#msg588619
I have to point out that this behavior also occurs with W7 firewall so beware.
-
I will wait until this problem is sorted out before I update to Avast 7.
-
I will wait until this problem is sorted out before I update to Avast 7.
Well, avast6 also have this "problem".
-
I will wait until this problem is sorted out before I update to Avast 7.
Well, avast6 also have this "problem".
Perhaps you don't really understand the problem, but I can assure you, this issue doesn't exist in Avast 6.
-
Hi,
I agree with Dogstar,
This issue is not present in Avast 6
-
Hi. The suggestion to
enable "Scan traffic from well-known browser processes only" in Web Shield Expert Settings
i think is the best work around for now.
I did discover however (using Snagit v11 in this example) that if i first left the "Scan traffic from well-known browser processes only" option enabled and did an "upgrade check" from within Snagit that a pop up from Comodo would appear (the option to "Remember me" i would leave unticked).
If i then disabled the "Scan traffic from well-known browser processes only" option, Comodo popup DID NOT appear and access was granted. Of coarse the whole point of this thread is that this should not happen.
Now the important bit. If i now re-enable the "Scan traffic from well-known browser processes only" option and run the "Upgrade check" from within Snagit, access is now also granted without warning whereas before, it didn't?? Somehow the previous illegal "allow" is remembered. I guessed that a reboot would fix this and sure enough it did.
So it seems that by testing this issue by turning the "Scan traffic from well-known browser processes only" on and off in one session will in itself wreak havoc and give undesired results.
So to summarise, enable "Scan traffic from well-known browser processes only" in Web Shield Expert Settings and reboot. Now run your tests and see if this solves your issues.
Hope this helps.
-
Hi,
Tried Release 2 and the problem still persists.
-
Hi,
an program update was available today.
I installed it. (I was running Avast 7 R2)
The problem still persists.
My Firefox and Thunderbird still work normally (With no rules or explicit block rules, except https is blocked in FF though)
I have "Scan traffic from well-known browser processes only" Enabled, but I'm pretty sure the Mozilla processes are Very well known.
I really hope a Fix will be presented, or at least a reason why not.
At the moment I feel that Avast is not even aware of this issue, nor do they care.
-
Same issues here, had to roll back to version 6 so comodo would function correctly.
This is a serious issue and should have been addressed immediately, as it also effects other firewalls as well, like windows 7's firewall.
Not to mention most with this issue wouldn't even be aware of it...
-
Well, indeed I have to admit there are some changes in Web Shield behavior as I have a minor problem with it (not this one), but it does not happen with my Vista machine, only with Win7 machine.
What are your OSes, all have Win7? And all have Comodo in your computer?
-
Well, indeed I have to admit there are some changes in Web Shield behavior as I have a minor problem with it (not this one), but it does not happen with my Vista machine, only with Win7 machine.
What are your OSes, all have Win7? And all have Comodo in your computer?
From what I've seen and read, the problem is specific to Windows 7/Avast 7 (web-Shield)/Comodo and Windows 7 firewall. Does anyone know if Comodo use Windows 7 Base Filtering Engine?
-
Have they worked out if this is Windows 7 32-bit or 64-bit or both yet?
Pretty sure Comodo doesn't use the W7 Base Filtering Engine since I imagine it wouldn't be so good if it did, its not like Windows 7 Firewall Control which apparently also has this bug conflict with the new Avast! 7 Web Shield and besides Comodo FW installs the entire bulk of CIS so why would it as an overly full third party FW?
-
Have they worked out if this is Windows 7 32-bit or 64-bit or both yet?
Pretty sure Comodo doesn't use the W7 Base Filtering Engine since I imagine it wouldn't be so good if it did, its not like Windows 7 Firewall Control which apparently also has this bug conflict with the new Avast! 7 Web Shield and besides Comodo FW installs the entire bulk of CIS so why would it as an overly full third party FW?
I was just curious about the reasons why, both CIS and the built in Windows 7 firewall, have the same problem. It seems logical to conclude there's some shared functionality. As a number of third-party firewalls use the base Microsoft code, this was a natural assumption. As far platform, it affects both 32 bit and 64 bit versions.
-
no solution yet?
-
Hi Hardov,
No Solution yet... Not even a response from a Avast team member.
Two work-arounds:
Disable Webshield. - Comodo will work perfectly, but no web traffic will be scanned.
Enable "Scan traffic from well-known browser processes only" - This will allow Most connections to be blocked by Comodo, but popular software like Mozilla and Thunderbird will go through unhindered.
-
Hi Hardov,
No Solution yet... Not even a response from a Avast team member.
Two work-arounds:
Disable Webshield. - Comodo will work perfectly, but no web traffic will be scanned.
Enable "Scan traffic from well-known browser processes only" - This will allow Most connections to be blocked by Comodo, but popular software like Mozilla and Thunderbird will go through unhindered.
Ok thanks so muchs for the help!
-
Hi All,
Updated to the latest version today.
Cleared my rules and tried again.
Firefox still connects like there isn't a care in the world even though it is explicitly blocked and Comodo logs it as blocked.
-
Hi guys,
this is really very interesting. Matousec's leak tests show 100% for COMODO, yet, apparently the firewall is not able to catch a Web proxy which our WebShield is.
I am not saying that Comodo is a bad firewall, on contrary, it is highly regarded, but maybe this might be a contribution to the relevancy of the leak tests -- as I see it from my brief glimpse on this issue, any program acting in the same way as avast does can overcome the firewall rules. Somewhat surprising for a product with such high leak-test "certification".
Concerning the fix from avast! side: I doubt we would fix this, making changes in the code, so that other firewalls block our traffic is exactly the opposite what we try to do.
Nice comment on the Comodo forum from the moderator though:
Re: Comodo Does not work with Avast 7!
« Reply #3 on: February 24, 2012, 06:27:55 AM »
This seems like an issue with Avast.
They changed the code. They will have to fix it.
I only hope that malware and unwanted programs follow the same guideline.
Lukas.
-
Well,no problems here...my firewall is on medium....and i have turned on block fragmented IP [since i dont use printers]... :)
-
Hi Lukor,
Thanks for your comment on this!
Regarding Matousec... I do not trust in the legitimacy of those tests anymore.
According to them Comodo is the only FW that works and everything else is crap... Different firewalls work in different ways and I believe their testing to favour certain Firewalls more than others....
But Comodo is a good and very popular FW.
That being said, I believe there to be a very large number of users affected by this and it's a serious issue.
I bug report has been submitted to Comodo, but there has been no sign of a fix anywhere.
-
Hi Hellion,
we have changed one driver in the v7. We abandoned the old and not supported TDI interface and started to use the new one (well, its already a few years old, but still newer) - WFP. I bet this is why Comodo has now troubles filtering our proxy requests and while at the same time allows traffic from the avastsvc.exe (where WebShield is hosted) these things together create that hole.
I would love to help Comodo understand the method we currently use and help them change the firewall in such a way that they are able to see and block that - should I be contacted by anyone.
The method we use is fully supported and documented and from several meetings with other companies I know for sure there are several (if not many) major products out there that use the same - so I guess such fix in Comodo will help not only Avast users but also many others.
L.
-
Hi Lukor,
Thanks, that was very clarifying.
Here is the Comodo forum discussion - https://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.60.html
Here is the Comodo Bug report - https://forums.comodo.com/bug-reports-cis/cis-firewall-fails-to-block-connections-for-blocked-applications-with-avast-7-t82440.0.html
-
Hi All,
Well,no problems here...my firewall is on medium....and i have turned on block fragmented IP [since i dont use printers]... :)
@ Winmaltech,
You do know that streaming video also uses Fragmented IP packets
-
Nice comment on the Comodo forum from the moderator though:
Re: Comodo Does not work with Avast 7!
« Reply #3 on: February 24, 2012, 06:27:55 AM »
This seems like an issue with Avast.
They changed the code. They will have to fix it.
I only hope that malware and unwanted programs follow the same guideline.
Lukas.
LOL ;D
-
Thanks for posting lukor. I'm not sure if you noticed my earlier post, but this is not confined to Comodo, it also affects Windows 7 built in firewall, which obviously uses the Windows Filtering Platform. So, the question is, as I asked earlier, does Comodo use WFP and, if so, does this mean that any firewall, also using WFP, can be bypassed by this change?
By the way, the Matousec tests are HIPs tests, not firewall tests, which is why they're completely irrelevant.
-
PrivateFirewall is also affected.
-
No issues with online armor...
-
Nice comment on the Comodo forum from the moderator though:
Re: Comodo Does not work with Avast 7!
« Reply #3 on: February 24, 2012, 06:27:55 AM »
This seems like an issue with Avast.
They changed the code. They will have to fix it.
I only hope that malware and unwanted programs follow the same guideline.
Lukas.
LOL ;D
yeah I already had a good laugh about that ROFL ;D
-
Hi guys,
this is really very interesting. Matousec's leak tests show 100% for COMODO, yet, apparently the firewall is not able to catch a Web proxy which our WebShield is.
I am not saying that Comodo is a bad firewall, on contrary, it is highly regarded, but maybe this might be a contribution to the relevancy of the leak tests -- as I see it from my brief glimpse on this issue, any program acting in the same way as avast does can overcome the firewall rules. Somewhat surprising for a product with such high leak-test "certification".
Concerning the fix from avast! side: I doubt we would fix this, making changes in the code, so that other firewalls block our traffic is exactly the opposite what we try to do.
Nice comment on the Comodo forum from the moderator though:
Re: Comodo Does not work with Avast 7!
« Reply #3 on: February 24, 2012, 06:27:55 AM »
This seems like an issue with Avast.
They changed the code. They will have to fix it.
I only hope that malware and unwanted programs follow the same guideline.
Lukas.
What about Online Armor Free? can we use Online Armor free?
-
What about Online Armor Free? can we use Online Armor free?
Your sig states that your already using OA ::) it's working isnt it ??? Outpost firewall works good too
-
What about Online Armor Free? can we use Online Armor free?
Your sig states that your already using OA ::) it's working isnt it ??? Outpost firewall works good too
i dont know , im not a expert ;D
-
Hardov.
OA is ok. Up to now this behavior is affecting only Windows 7 64 bit using Windows firewall, Comodo FW, and now there is a new report that Private firewall is affected.
-
Online Armor is not affected as seen in https://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.15.html Reply 28 / 47. I have Outpost in another pc and it's not affected. Seems to be affecting x64 systems. I have Online Armor Premium ver5.5 with Avast IS Build 1426 on an Win7 x32 and it's not affected. My other x32 with AvastFree and CIS ver5.9 seems to be functioning okay. I can block FF in CIS>Firewall rule while I have Avast WebShield enabled.
In my CIS FF is set as "web browser"(built-in rule in Comodo). The same rule I use for Google Chrome and IE/Opera. I tried to set it at "Blocked application" in Comodo and CIS blocks the connection and launching of the browser. On an x64 pc it ain't like that.
-
are you guys setting any rules for the localhost communication. since it is actually the connection between the browser and Webshield that you want to control and it is between 127.0.0.1:xxxx and 127.0.0.1:12080, so really are your firewalls able to block the localhost traffic, or control it - are you sure you don't have there some big rule allowing all trafic inside the computer (localhost only) etc.
-
are you guys setting any rules for the localhost communication. since it is actually the connection between the browser and Webshield that you want to control and it is between 127.0.0.1:xxxx and 127.0.0.1:12080, so really are your firewalls able to block the localhost traffic, or control it - are you sure you don't have there some big rule allowing all trafic inside the computer (localhost only) etc.
Thanks for the reply.
1.This didn't happen using Avast 6, it's a specific 'issue' with Avast 7.
2. Some Applications specifically require access to loopback for internal communication, for example firefox.
3. Creating a specific rule to block all localhost communication, for IE, had no effect.
By the way, this 'issue' affects 32 bit and 64 bit Windows 7.
-
As I've said before - avast7 uses different driver API to do the redirection. It really depends on the firewall how they do treat that. Maybe before, with avast6 Comodo was not even aware of the fact, that the browser is not really connecting to the Internet (instead making only localhost connection to the scanning proxy) and hence it treated it with its outbound rules. Just guessing though.
Maybe a rule with "incoming connections to avastsvc.exe - ASK" will solve that.
-
I highly recommend that you use only avast or comodo firewall. In my opinion, avast is enough. You do not need to install any third-party firewall. Installing many firewall softwares does not insure that your computer is well-protected. In addition to that, there will occur conflicts between the sofwares which will slow your computer down or even cause the blue screen of death! :)
-
You do not need to install any third-party firewall.
True, but we're talking about avast! Free or Pro here. ;)
-
You do not need to install any third-party firewall.
True, but we're talking about avast! Free or Pro here. ;)
Second Asyn statement, and add that W 7 firewall is also affected so It is a must to have a working third party firewall with Avast! Free or Pro.
-
Hi All,
Please note that CIS was updated to version 5.10.228257.2253.
This issue with Avast and Comodo Firewall is still very much present.
-
Cool....i was waiting for an update coz i want 2 install the comodo firewall n use avast free alongside......so u mean that comodo have fixed the problem with avast and both r working fine?????
-
Cool....i was waiting for an update coz i want 2 install the comodo firewall n use avast free alongside......so u mean that comodo have fixed the problem with avast and both r working fine?????
No, Comodo has not fixed it yet. This issue is still happening with a few FW. If running Avast! 7 free under W 7 better get OA or Outpost.
-
Hi All,
Sorry edited my previous post as it made no sense.
-
I have no problem whatsoever. I installed Avast 7 first, then I rebooted and installed Comodo Firewall.
I read somewhere years ago that its better to install Avast first then only install Comodo Firewall.
But I am not sure.
-
I want to upgrade to Avast 7, but there's no point if it's going to mess up Comodo. I hope this problem gets sorted out soon.
-
Like to add latest version 5.10.228257.2253 blocks FF 11.0 if policy is set through Firewall>Network Security Policy. Change is made @ FF line from Web browser to Blocked Application and works as it should. FF is blocked. Changing setting back to Web Browser restores connectivity.
Bug in COMODO firewall does only seem to affect Win 7 systems from what I've seen here. What I'd like to find out why this is so, and why Win Firewall is also affected in Windows 7.
Bug does not seem to affect XP versions.
-
Hi guys,
Concerning the fix from avast! side: I doubt we would fix this, making changes in the code, so that other firewalls block our traffic is exactly the opposite what we try to do.
Lukas.
So in making this statement i would have to take it that Avast does not see this as a security issue?? When you consider all of the unsuspecting, don't know otherwise Avast users around the world that are using Windows Firewall, Comodo Firewall and a couple of others mentioned such as Private Firewall
-
So in making this statement i would have to take it that Avast does not see this as a security issue?? When you consider all of the unsuspecting, don't know otherwise Avast users around the world that are using Windows Firewall, Comodo Firewall and a couple of others mentioned such as Private Firewall
It means Firewalls should be able to block it, or malware also can bypass Firewalls. It is Firewalls' fault (security hole).
Fixing avast to be blocked by Firewalls does not solve this problem. No one wants malware to bypass Firewalls using same technique.
-
I get what you are saying, so the reality is without beating around the bush Comodo and Windows Firewall aren't up to scratch security wise and as i have read Online Armour is the one to have? Sorry i just need to hear the cold hard facts so i can make a sound decision without pussy footing around.
-
PrivateFirewall, Outpost Firewall and Online Armor all work fine with avast, iv been testing all of them this week :)
Its' also just the outbound protection of the windows firewall that causes some problems but in it's default state it works fine.
-
Thank you both, sorry for being a blunt. I just got to my wits end dredging through threads not only here and running multiple scenarios myself to try and sort it that it got to a stage i just needed some straight answers.
My apologies and thank you both
-
You're welcome.
-
PrivateFirewall, Outpost Firewall and Online Armor all work fine with avast, iv been testing all of them this week :)
Its' also just the outbound protection of the windows firewall that causes some problems but in it's default state it works fine.
Craig, of these 3 third party firewalls, which is likely to be the quietest after the initial learning period? As per my signature, you can see that I'm using Sygate and it's catching changes to Firefox, etc. after they are updated and asking. However, it's been EOL for some time now.
-
PrivateFirewall, Outpost Firewall and Online Armor all work fine with avast, iv been testing all of them this week :)
Its' also just the outbound protection of the windows firewall that causes some problems but in it's default state it works fine.
Craig, of these 3 third party firewalls, which is likely to be the quietest after the initial learning period? As per my signature, you can see that I'm using Sygate and it's catching changes to Firefox, etc. after they are updated and asking. However, it's been EOL for some time now.
Even though i have a Pro license for Outpost which the latest version 7.5.2 i think is there best version yet for compatibility and system lightness but i think i still prefer Privatefirewall more. I only recieved a couple of popups which were for my mobile broadband and Total Media Theater in that whole week of testing and the lightness on the system was excellent, it feels lighter than the windows firewall.
Theres a very informative pdf file on there website that is well worth downloading and reading, good to keep for future refrence :)
http://www.privacyware.com/PF_support.html
-
Thanks, Craig. I have Private Firewall install and the pdf downloaded. I'll read thru the pdf, and likely change over to it sometime this next week.
-
Thanks, Craig. I have Private Firewall install and the pdf downloaded. I'll read thru the pdf, and likely change over to it sometime this next week.
No worries, enjoy :)
Just to update you PrivateFirewall doesn't stealth my ports properly with mobile broadband but does work fine with routered connections, Outpost is superior concerning mobile broadband.
-
I also having the problem, avast webshield with comdo firewall. Is there is any fix available other than disabling the webshield in avast
-
@Paroh
Read your other post
http://forum.avast.com/index.php?topic=95782.msg764070#msg764070
-
Outpost is superior concerning mobile broadband.
+1 I strongly agree with craigb as I have mobile broadband too using Outpost Pro, craigb did you get yourself a lifetime license when you got your Outpost Pro FW :)
-
Outpost is superior concerning mobile broadband.
craigb did you get yourself a lifetime license when you got your Outpost Pro FW :)
Sure did, bought two of them for $30 each if i remember correctly :)
-
Here is a reply from the comodo developers about the situation
Hello Guys,
The issue is avast intercepts WEB connections at the driver level and redirects connections to its own local proxy.
Because CIS operates at NDIS layer i.e. the lowest layer of the protection, it sees the actual connection i.e. avast proxy. Normally CIS should have blocked the loppback area connection to the proxy however because of the limitations in Windows 7, it fails.
CIS uses TDI, WFP and NDIS to provide its firewall functionality. WFP maybe enough ti implement an average firewall but it is not enough for a firewall like CFW so that it could not be used alone wihtout the support of the other 2 technologies. Windows 8 allowed us to use WFP more than previous windows editions and it should not be a problem with the next CIS editions which support Windows 8.
-
Hello Guys,
The issue is avast intercepts WEB connections at the driver level and redirects connections to its own local proxy.
Because CIS operates at NDIS layer i.e. the lowest layer of the protection, it sees the actual connection i.e. avast proxy. Normally CIS should have blocked the loppback area connection to the proxy however because of the limitations in Windows 7, it fails.
CIS uses TDI, WFP and NDIS to provide its firewall functionality. WFP maybe enough ti implement an average firewall but it is not enough for a firewall like CFW so that it could not be used alone wihtout the support of the other 2 technologies. Windows 8 allowed us to use WFP more than previous windows editions and it should not be a problem with the next CIS editions which support Windows 8.
That's nice, but how about fixing CIS so it will work with windows 7?
-
Hello all!
I can confirm this, I made a lot of tests: this is an exclusive Avast bug. The same behaviour written in first post it happens with:
Avast 6 OR Avast 7,
Comodo OR Privatefirewall,
Win 7 OR Vista,
in any combination.
So, this is not a matter of Comodo or Privatefirewall, Seven or Vista problem. The sole common factor in all combinations is Avast, 6 OR 7. When Avast is disabled and the common factor gone, all the setups are working well.
And a little offtopic: beggining with the first release of Avast v.7 and its database (available for v.6, too), many well known apps, like FotoSketcher, UltraISO, WinTools.net and Cool Edit (yeah, I now, it's old) are detected by sandbox as possible dangers.
I think this version of Avast was made in a big hurry and without the old respect for this brand, sorry.
Tnank you for your attention!
-
So it's an "exclusive Avast bug" that only occurs in combination with other products. :o
(My brain hurts!)
-
Hello all!
I can confirm this, I made a lot of tests: this is an exclusive Avast bug. The same behaviour written in first post it happens with:
Avast 6 OR Avast 7,
Comodo OR Privatefirewall,
Win 7 OR Vista,
in any combination.
Privatefirewall works fine with avast, i spent a week recently testing that firewall and no problems at all except for detection of mobile broadband networks.
You need to add exclusions between avast and privatefirewall for them to function correctly, outpost and online armor firewalls also function without problems so i believe the problem lie's with comodo but im not willing to test that one :)
-
Well for me the First post in this shows an inadequacy in the firewall if it can't determine the process using the localhost proxy.
I did a simple test, blocked the network connection for firefox.exe in my Firewall Outpost Firewall Pro (image1) and then tried to read unread posts (image2) and no content. So it wasn't able to tunnel through the avastSvc.exe proxy undetected.
-
So it's an "exclusive Avast bug" that only occurs in combination with other products. :o
(My brain hurts!)
Yes, THIS specific bug, in this thread, is exclusevly related to Avast. The combinations only, and only them, with a single constant, reveal the "owner" of the bug. You'll not be able to know there is a bug in a soft if this is only on your cd or dvd. There, in dvd case, all softs are perfect. Your brain hurts because you have it AND you feel it. And yet, only the brain hurts, exclusively...
It hurts, ah?
Hello all!
I can confirm this, I made a lot of tests: this is an exclusive Avast bug. The same behaviour written in first post it happens with:
Avast 6 OR Avast 7,
Comodo OR Privatefirewall,
Win 7 OR Vista,
in any combination.
Privatefirewall works fine with avast, i spent a week recently testing that firewall and no problems at all except for detection of mobile broadband networks.
You need to add exclusions between avast and privatefirewall for them to function correctly, outpost and online armor firewalls also function without problems so i believe the problem lie's with comodo but im not willing to test that one :)
Thank you, I'll try, perhaps. But too many headaches :D for an AV. Maybe it's time to change. Or go back to the 4.8. :-\ Thank you again.
-
Hi All,
@Sceleron.
No need to go to 4.8. Version 6 works just fine.
Also, this issue is caused by avast, but should be fixed by Comodo.
It's shocking that a proxy service is able to bypass their Firewall... What a disgrace.
What's even worse is that this bug has been live for so long and they have done Nothing!.
-
So it's an "exclusive Avast bug" that only occurs in combination with other products. :o
(My brain hurts!)
Yes, THIS specific bug, in this thread, is exclusevly related to Avast. The combinations only, and only them, with a single constant, reveal the "owner" of the bug. You'll not be able to know there is a bug in a soft if this is only on your cd or dvd. There, in dvd case, all softs are perfect. Your brain hurts because you have it AND you feel it. And yet, only the brain hurts, exclusively...
It hurts, ah?
I got/get what you're saying. All I meant was that the problem can't simultaneously be "exclusive" and occur "in any combination".
'Exclusive" means, (a) on it's own, (b) not with or apart from anything else.
Ergo, "exclusive" use of AIS 7.0.1426 causes me no problems on My Windows 7 machines.
As well I don't think it's best described as a "bug" in avast!
If any antivirus using MS approved methods and APIs can bypass the outbound monitoring of a firewall (Microsoft's or Comodo's), I tend to think that fixing it should be a priority for the vendor of the functionally-compromised component.
-
Wish I had found this thread before I asked about installing Avast Internet Security without it's firewall earlier today.
I see nothing but the blame game going on here, but simply it looks like don't use the vsn 7... end of story.
WELL, I did pay for a 2 year license a few hours ago BUT NOW I CAN'T download the Internet Security version at all (not a copy that works at least).
Just comes up with an error 1006. NO MATTER WHICH method / browser I use, same problem when it tries to auto extract on VISTA. And yes everything that normally may interfere with the download is switched off / shut down.
So, with a half dozen downloads I'm just paying out for wasted bandwidth and apparently for a software combination that doesn't work anyway.
Also why oh why do they send an EXE file instead of a zip?
Now I have to go through the charge-back hoops... and no AV S/W.
-
Wish I had found this thread before I asked about installing Avast Internet Security without it's firewall earlier today.
I see nothing but the blame game going on here, but simply it looks like don't use the vsn 7... end of story.
WELL, I did pay for a 2 year license a few hours ago BUT NOW I CAN'T download the Internet Security version at all (not a copy that works at least).
Just comes up with an error 1006. NO MATTER WHICH method / browser I use, same problem when it tries to auto extract on VISTA. And yes everything that normally may interfere with the download is switched off / shut down.
So, with a half dozen downloads I'm just paying out for wasted bandwidth and apparently for a software combination that doesn't work anyway.
Also why oh why do they send an EXE file instead of a zip?
Now I have to go through the charge-back hoops... and no AV S/W.
Sorry I don't see how the problem, that some firewalls (COMODO e.g.) does not support Windows7 redirect API and is not handle to filter such network events is related to the situation where you are not able do complete the download. Maybe you might want to start a different thread, I bet there are millions of people who were able to download Avast AIS from our servers.
-
Guy, I want to clarify few things here:
Avast version 7 uses supported API of Windows 7, that is created solely for the purpose of redirecting network connections. It uses it to redirect connections. It is new in avast7, however Windows7 is not such a brand new OS and the redirect api (REDIRECT layers in WFP) are there since the Win7 launch (2 years? More?). There is no other supported way of doing it.
In some of the previous comments from COMODO, they said they use TDI as well as WFP on Win7 and stated that they are not able to fully filter all traffic on Windows 7. TDI interface is entirely deprecated with Windows 7 and almost banned in Windows 8 (no compatibility Logo with TDI drivers for example, performance hits on Win7). Avast is trying to be more compatible and nicer to newer OSs and this is why we are also trying to eliminate TDI drivers from our code and replace it with the Microsoft supported equivalents. The first step was this redirect driver, previously on TDI, now correctly on WFP.
We will never change it back and will continue to remove other TDI drivers from our products.
Thanks.
Lukas.
-
A worrying trend, out of context comments by a product rep to defend a problem.
I didn't at all infer the topic of this thread was the cause of the download probs.
Just that had I read it earlier I wouldn't have wanted to risk paying for the new product at all. It's apparently dodgy enough to avoid especially for VISTA it seems.
As for the download probs, you have the error code I noted above and I keep getting it after all downloads via multiple different download mechanisms.
So I've just paid for a 1 year license of "Pro" which applied to the trial install without hassle. That will get me by why I continue the check out AV programs!
-
A worrying trend, out of context comments by a product rep to defend a problem.
I didn't at all infer the topic of this thread was the cause of the download probs.
Just that had I read it earlier I wouldn't have wanted to risk paying for the new product at all. It's apparently dodgy enough to avoid especially for VISTA it seems.
As for the download probs, you have the error code I noted above and I keep getting it after all downloads via multiple different download mechanisms.
So I've just paid for a 1 year license of "Pro" which applied to the trial install without hassle. That will get me by why I continue the check out AV programs!
Hi Wombat,
Lukor is an avast team member with detailed knowledge of how the Avast software operates.
This thread is about Comodo being unable to keep up with Windows and Avast.
Your Download issue is quite the anomaly, I've never had problems downloading avast. Have you tried downloading from another machine?
Please open a NEW thread and see if any good suggestions come up.
-
Hello!
Thank you all, I mean all, indeed. Avast forum is a place ;)...
I've managed the situation, somehow. I use, most of the time, Privatefirewall and, with it, the things can be managed to work. But. I think I'll change the AV, yet. I use avast since v4.7. I do not like or trust this Avast, sorry to say this.
Off: From today, Hijackthis is blacklisted as potentially dangerous... What to say?
Thank you, once again.
-
A worrying trend, out of context comments by a product rep to defend a problem.
I didn't at all infer the topic of this thread was the cause of the download probs.
Just that had I read it earlier I wouldn't have wanted to risk paying for the new product at all. It's apparently dodgy enough to avoid especially for VISTA it seems.
As for the download probs, you have the error code I noted above and I keep getting it after all downloads via multiple different download mechanisms.
So I've just paid for a 1 year license of "Pro" which applied to the trial install without hassle. That will get me by why I continue the check out AV programs!
Hi Wombat,
Lukor is an avast team member with detailed knowledge of how the Avast software operates.
This thread is about Comodo being unable to keep up with Windows and Avast.
Your Download issue is quite the anomaly, I've never had problems downloading avast. Have you tried downloading from another machine?
Please open a NEW thread and see if any good suggestions come up.
Don't use Comodo if you hate it so much! Use something else! They didn't fix it yet? Well they won't fix it now... Comodo AV is better in detection rate than Avast AV... Fact... But not so good at browser malware blocking... And what the hell you mean by Comodo is unable to keep up with Windows and Avast?
-
Don't use Comodo if you hate it so much! Use something else! They didn't fix it yet? Well they won't fix it now... Comodo AV is better in detection rate than Avast AV... Fact... But not so good at browser malware blocking... And what the hell you mean by Comodo is unable to keep up with Windows and Avast?
Hi Seany007,
You should find the answer to your question:
And what the hell you mean by Comodo is unable to keep up with Windows and Avast?
In Lukor's post:
In some of the previous comments from COMODO, they said they use TDI as well as WFP on Win7 and stated that they are not able to fully filter all traffic on Windows 7. TDI interface is entirely deprecated with Windows 7 and almost banned in Windows 8 (no compatibility Logo with TDI drivers for example, performance hits on Win7). Avast is trying to be more compatible and nicer to newer OSs and this is why we are also trying to eliminate TDI drivers from our code and replace it with the Microsoft supported equivalents. The first step was this redirect driver, previously on TDI, now correctly on WFP.
Also...
Comodo AV is better in detection rate than Avast AV... Fact...
This thread has NOTHING to do with ANTI-Virus detection, it's a Firewall issue.
-
Don't use Comodo if you hate it so much! Use something else! They didn't fix it yet? Well they won't fix it now... Comodo AV is better in detection rate than Avast AV... Fact... But not so good at browser malware blocking... And what the hell you mean by Comodo is unable to keep up with Windows and Avast?
Hi Seany007,
You should find the answer to your question:
And what the hell you mean by Comodo is unable to keep up with Windows and Avast?
In Lukor's post:
In some of the previous comments from COMODO, they said they use TDI as well as WFP on Win7 and stated that they are not able to fully filter all traffic on Windows 7. TDI interface is entirely deprecated with Windows 7 and almost banned in Windows 8 (no compatibility Logo with TDI drivers for example, performance hits on Win7). Avast is trying to be more compatible and nicer to newer OSs and this is why we are also trying to eliminate TDI drivers from our code and replace it with the Microsoft supported equivalents. The first step was this redirect driver, previously on TDI, now correctly on WFP.
Also...
Comodo AV is better in detection rate than Avast AV... Fact...
This thread has NOTHING to do with ANTI-Virus detection, it's a Firewall issue.
Right but the firewall issue only if you using Avast 7 shields with Comodo Firewall? Right? The bypass? If say you will use Comodo AV and Comodo Firewall you won't have any problem? Right? So use Comodo AV instead of Avast! Done! That's what I wanted to say... Since Comodo AV is even better...
-
Guys i think i have found a solution to override the problem until Avast fix it.Adding comodo in exclusion lists does not work for some reason as you have probably noticed..
The problem is that when Webshield is enabled, comodo firewall does not block programs even if they do not use port 80.
So disabling problem causing webshield was an obvious solution, but then it would compromise your antivirus security..
Better solution is from Avast-RealtimeShields-Webshield-ExpertSettings-> Put a check "Scan traffic from well known browser processes only"
Now Comodo firewall will block traffic as it should supposed to..
-
@kocakafa: it still didn't work for me.....so i uninstalled comodo and using online armor free.....avast works fine with online armor you don't need to disable any shields of avast....
-
@kocakafa: setting 'Scan traffic from well known browser processes only' will allow comodo firewall to block all non-browser applications. however, browser applications like firefox, google chrome, IE will still be scanned by webshield. comodo firewall will not be able to block these browsers from internet access (bypassed).
@Seany007: u are obviously not getting the point...comodo firewall standalone is meant to be used with other antiviruses...the issue here is comodo firewall has a design flaw which allows connections going through proxy applications to bypass it (avast is an example here).
the usage of comodo internet security - antivirus + firewall + defence plus only provides an illusion that the problem is gone...what if u have another application which acts as a proxy and directs all other application connections to the internet through it? ur problem is back.
heard they (comodo) are fixing it sometime later. hope they do it asap.
-
Hi AntiVirusASeT,
heard they (comodo) are fixing it sometime later. hope they do it asap.
It's taken them bloody ages to fix this!
-
It isn't that the web shield doesn't work with comodo, but that currently comodo can't differentialt between the web shield proxy and programs being redirected through the proxy.
So if you have a set a block on a particular program from accessing the internet, if it is connecting to the internet using the http protocol over an http port, then that traffic would be routed through the web shield proxy so it can scan the content. Because comodo can't differentiate between the two and you have the web shield proxy (avastSvc.exe) allowed, the blocked program can connect.
Using latest stable versions of Avast and CFW on Win7 64 bits. Confirming the bug is still there as FF isn't blocked even when you block ALL web browsers from going on internet with CFW (Avast nor Comodo seem to want to put energy on this problem and the dispute on wheter one or the other is the culprit is still on!!!...) >:(. Switching back to Private firewall and keeping Avast (for the best, I hope).
-
Who can avast fix a problem that is on the comodo side. Also this is only an issue if you have firewall rules to block a program/s (many don't), other than that the web shield works in its protection as normal.
- see http://forum.avast.com/index.php?topic=93953.msg768135#msg768135 (http://forum.avast.com/index.php?topic=93953.msg768135#msg768135).
-
Thanks David and it seems Comodo is in deep trouble with reshaping their FW from scrap to make it work 100% protected on Win 7 64 bits system and on on Win 8. I installed and tested by blocking Firefox on Private Firewall on my system without a flaw. The problem has nothing to do with Avast web Shield but more with archaic Comodo FW ;)
-
You're welcome.
-
Just in case, from the Wilder's Security forum, if you use Private FW and want to make sure there is no conflict with Avast Web shield at all, just go to http://www.wilderssecurity.com/showpost.php?p=2076807&postcount=96 (http://www.wilderssecurity.com/showpost.php?p=2076807&postcount=96) and add the rules to your browsers properly. Of course, at this point, when you think of it, you'd may be better off :-[ using the AVAST FW in the paid version 8)
-
It isn't that the web shield doesn't work with comodo, but that currently comodo can't differentialt between the web shield proxy and programs being redirected through the proxy.
So if you have a set a block on a particular program from accessing the internet, if it is connecting to the internet using the http protocol over an http port, then that traffic would be routed through the web shield proxy so it can scan the content. Because comodo can't differentiate between the two and you have the web shield proxy (avastSvc.exe) allowed, the blocked program can connect.
Using latest stable versions of Avast and CFW on Win7 64 bits. Confirming the bug is still there as FF isn't blocked even when you block ALL web browsers from going on internet with CFW (Avast nor Comodo seem to want to put energy on this problem and the dispute on wheter one or the other is the culprit is still on!!!...) >:(. Switching back to Private firewall and keeping Avast (for the best, I hope).
I am interested, how did you check that? Did you select 'stop all traffic' in Comodo?
-
No, well, when you stop all traffic, it works. The problem is when you stop the specific program, your browsers, firefox, chrome etc... in the browser policy, in the firewall rules, well as reported in the forums the program isn't stopped at all and still connects to the internet. I don't suffer this with Private Firewall but still I slightly modified my browser rules to accomodate any chance in Avast Web Shield flaw ;D Here's the link to the specific thread in the Comodo forum:https://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.0.html;msg614543#msg614543 (https://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.0.html;msg614543#msg614543)
-
But it isn't a web shield flaw, avast is using the latest windows redirection API
Avast version 7 uses supported API of Windows 7, that is created solely for the purpose of redirecting network connections.
The problem is that comodo doesn't have support for that windows 7 API for the redirection of network connections.
From your previous experience it appears that PrivateFirewall has support for that Windows 7 (not avast's) API for the redirection of network connections.
-
So, did I do well following this tip ((with Private Firewall)from the Wilder's Security Forum :D):
--- Correction ---
Yes it is an Avast issue and the Avast forum is where you should be getting help from.
Here is how to prevent all non-Avast web shield filtered traffic on port 80 for your browser.
In your existing PF browser firewall rules:
You need to disable your existing browser PF Primary and Alternate HTTP Connections rules by by unchecking the H and L boxes.
Leave all your remaining browser rules as is; that includes the existing Secure HTTP Connection rule that connects to port 443! In the event you uninstall Avast or turn off its web shield, you will have to activate Primary and Alternate HTTP Connections rules and delete or deactivate the new rules you will add below.
You need to create 2 firewall rules for you browser to only allow HTTP traffic to Avast web shield proxy server:
Allow outbound - TCP - from local 1024-65355(user) port - to remote port 12080, remote IP 127.0.0.1 - checkmark IP address connection box only.
Deny Outbound -TCP - from any local port- to remote port 80, any remote IP - checkmark H and L boxes.
Move the two new rules to the top of the existing rule set.
That's it!
If these rules look weird remember that its avastsvc.exe that is doing the actual HTTP connections with Avast web shield turned on, not your browser.
?
-
Well if you hadn't done that and you didn't have a problem with privatefirewall, not to mention that is allowing the web shield.
I'm no firewall geek but as far as I can see there is nothing there to combat the whole point of this topic "Avast 7 and Comodo Firewall" blocked programs in comodo being able to sail through the avast proxy unmolested because comodo doesn't support the latest API.
All this does is ensure that privatefirewall doesn't block the web shield localhost proxy (controlled by avastSvc.exe). So it won't/shouldn't hurt, but I tend not to pre-empt a problem but react to them.
-
But it isn't a web shield flaw, avast is using the latest windows redirection API
Avast version 7 uses supported API of Windows 7, that is created solely for the purpose of redirecting network connections.
The problem is that comodo doesn't have support for that windows 7 API for the redirection of network connections.
Trying to understand this as the 'problem' discussed here also affects Windows 7 own firewall with outbound protection
where permission for avastsvc.exe lets all redirected browsers and other programs at port 80 through, making the 7 firewall
useless for outbound control when Avast Webshield is used. Windows 7 FW must support windows 7 API?
A solution for Window 7 firewall, Comodo and you name them would be to give Avast users the possibility to
determine which processes to redirect through Webshield. Not only the option to only scan 'well-known' browser processes.
As far as I remember we had something like that in earlier versions of Avast.
This would be much better than discussing who is at fault here.
-
Let's stop doing like ostrich and put our heads in the sand :). AILWIL, COMODO and even MICROSOFT should work on this intensively 8)
-
Is this issue fixed?
-
Is this issue fixed?
It will be fixed with the next release of Comodo, I'm not sure if Avast are doing anything about it though.
-
Is this issue fixed?
It will be fixed with the next release of Comodo, I'm not sure if Avast are doing anything about it though.
If it's a Comodo problem, why would Avast be doing anything about it ???
-
If it's a Comodo problem, why would Avast be doing anything about it ???
It's not just Comodo, it's windows firewall too. But that's already been talked about in this thread.
-
is the problem only with WebShield? am i fine using Avast without Web Shield together with Comodo?
what about Comodo Defense+, isn't it redundant if i'm using Avast Behavior and Script Shield with Cloud Services?
Network Shield is ok?
-
is the problem only with WebShield? am i fine using Avast without Web Shield together with Comodo?
what about Comodo Defense+, isn't it redundant if i'm using Avast Behavior and Script Shield with Cloud Services?
Network Shield is ok?
Webshield is one of the most important shields and your first line of defence so by no means should you disable it :o
If you have to have Comodo then i would suggest waiting for there next release or imo there are better firewalls such as Outpost, Online Armor, Privatefirewall which work great with avast.
-
Webshield is one of the most important shields and your first line of defence so by no means should you disable it :o
If you have to have Comodo then i would suggest waiting for there next release or imo there are better firewalls such as Outpost, Online Armor, Privatefirewall which work great with avast.
First line of defense? pardon my ignorance but doesn't it only scans Web Traffic, the sites you visit and etc? most of the exploits on the Web are either Java or Flash, am i wrong? from all this time using the Web Shield, browsing the sites i use on day-to-day basis i don't see the Web Shield being of much use.. i think the File system shield is the most important shield.. from the firewalls you've mentioned, which do you recommend? and you still haven't answered my questions from the last post
is the problem only with WebShield? am i fine using Avast without Web Shield together with Comodo?
what about Comodo Defense+, isn't it redundant if i'm using Avast Behavior and Script Shield with Cloud Services?
Network Shield is ok?
-
First line of defense? pardon my ignorance but doesn't it only scans Web Traffic, the sites you visit and etc? most of the exploits on the Web are either Java or Flash, am i wrong? from all this time using the Web Shield, browsing the sites i use on day-to-day basis i don't see the Web Shield being of much use.. i think the File system shield is the most important shield.. from the firewalls you've mentioned, which do you recommend? and you still haven't answered my questions from the last post
is the problem only with WebShield? am i fine using Avast without Web Shield together with Comodo?
what about Comodo Defense+, isn't it redundant if i'm using Avast Behavior and Script Shield with Cloud Services?
Network Shield is ok?
hi Fell_MTK,
Just to show you how important WebShield is, see the attached below: Was visiting an anti-malware site with high reputation at the time (still is), so the last thing one would think would be a trojan lurking in a tiny url embedded in the blog post. :o
WebShield is an external facing (internet) filtering shield, File shield is internal, Network is primarily internal (home network) and host computer. So, without WebShield active, I would've been nailed to the wall with this one.
Recommend enabling WebShield to prevent a web page from loading when it is malicious. WebShield off, malicious page loads like no tomorrow and you are done.
Are you ready to repair or re-install the os if needed?
-
Webshield is one of the most important shields and your first line of defence so by no means should you disable it :o
If you have to have Comodo then i would suggest waiting for there next release or imo there are better firewalls such as Outpost, Online Armor, Privatefirewall which work great with avast.
and you still haven't answered my questions from the last post
I believe i have answered as webshield is your first line of defence, there are more troubles on the net than just java and flash - what about Malware ( viruses, trojans ) coming from infected webpages :o as mentioned you should definitely not disable the webshield, i'd rather stick to the default windows firewall with no outbound protection than disabling the webshield.
Iv got two lifetime licenses for outpost pro firewall so that would obviously be my first recommendation but the free version requires you to install the free suite in custom install without all the others features as there is no stand alone free firewall, my next choice would be Online Armor which has a free standalone version.
-
Comodo FW has been a real pain in the arse and I'm so glad I gave up long ago since v5.5 something since I was a long time user from v3.14 up to v5.5, it was killing my PC as hell and I gave up than I decided to buy a lifetime licence of Outpost Pro FW smooth as baby oil rubbing your backside so you can slide across the floor easy ;)
-
smooth as baby oil rubbing your backside so you can slide across the floor easy ;)
Are we recommending firewalls or baby oil ??? ;) what you do at home with baby oil Speedy should be kept private ;D
-
smooth as baby oil rubbing your backside so you can slide across the floor easy ;)
Are we recommending firewalls or baby oil ??? ;) what you do at home with baby oil Speedy should be kept private ;D
Well, maybe he can teach us some new tricks... ;D ;)
-
Well, maybe he can teach us some new tricks... ;D ;)
Iv know several tricks but there not for a public forum :-X ;D
-
I'm not that dirty ;D Comodo FW has given my PC to much rust and it can't run any smoother, because it keep slowing down like a crash dummy in a car in slow motion. That why I used Outpost Pro FW because it keep my PC running smooth as it glide much easier, beside my PC in my baby that why I have to look after it keep it clean and tidy using baby oil for some PC hardware parts from going rusty.
-
i have installed OA Free, it comes with its own Web Shield, Keylogger and Program Guard, should i disable them or there isn't any compatibility issue with avast?
-
As far as I know I have only Window's Firewall. Is that enough protection?
I have Windows 7 64 bit SP1 and my husband uses XP 64 bit SP3. His computer is connected through my router and he too has only Window's Firewall.
I wouldn't have any idea of how to use any of the firewalls that were mentioned in this topic.
??? :-[
-
i have installed OA Free, it comes with its own Web Shield, Keylogger and Program Guard, should i disable them or there isn't any compatibility issue with avast?
OA's shield work differently to avast so all you have to do is exclude OA in the avast file system shield and all the avast processes in OA should be set to allow all.
-
As far as I know I have only Window's Firewall. Is that enough protection?
I have Windows 7 64 bit SP1 and my husband uses XP 64 bit SP3. His computer is connected through my router and he too has only Window's Firewall.
I wouldn't have any idea of how to use any of the firewalls that were mentioned in this topic.
??? :-[
If you dont really understand firewalls then your better off sticking with the windows firewall as the win7 firewall is quite good, as for your husbands system im not sure if any of the firewalls mentioned will be compatable with 64bit xp.
-
W7 firewall is quite good as Craigb said, however XP windows firewall is not very good because it doesn't block outbound traffic this is why you need a 3rd party firewall that control and monitored both traffic inbound and outbound traffic not just one traffic.
-
...as for your husbands system im not sure if any of the firewalls mentioned will be compatable with 64bit xp.
Yes, XP 64bit is a quite "exotic" OS and rarely supported.
@midnight: There's no SP3 for XP 64bit, so you should recheck your husband's OS...!!! ;)
-
Sorry to necro such topic but is the issue between avast web shield and windows 7 firewall fixed or not at all? please do not tell me to search since after nearly 20 minutes i got this thread.
Please also do not tell me to use another firewall for better outbound control.
Thanks
-
Hi Soulfear and welcome to Avast! forum.
http://forum.avast.com/index.php?topic=109571.msg863496#msg863496
-
hi iroc9555,
thanks for the welcome.
that post leads to comodo fw and avast.
my question was the windows 7 firewall issue that was initially an issue.
thank you for the help.
-
hi iroc9555,
thanks for the welcome.
that post leads to comodo fw and avast.
my question was the windows 7 firewall issue that was initially an issue.
thank you for the help.
That post also states at the beginning:
If you are running Windows 7 make sure you got CIS 5.12 ( Firewall and D+ only. No AV ) to have complete control on your outbound connections...
That was the issue between Avast! and Comodo running in W7. No outbound control over program connections.
-
Webshield is one of the most important shields and your first line of defence so by no means should you disable it :o
If you have to have Comodo then i would suggest waiting for there next release or imo there are better firewalls such as Outpost, Online Armor, Privatefirewall which work great with avast.
and you still haven't answered my questions from the last post
I believe i have answered as webshield is your first line of defence, there are more troubles on the net than just java and flash - what about Malware ( viruses, trojans ) coming from infected webpages :o as mentioned you should definitely not disable the webshield, i'd rather stick to the default windows firewall with no outbound protection than disabling the webshield.
Iv got two lifetime licenses for outpost pro firewall so that would obviously be my first recommendation but the free version requires you to install the free suite in custom install without all the others features as there is no stand alone free firewall, my next choice would be Online Armor which has a free standalone version.
Filehippo shows there is a free standalone version of outpost. :-\
It seems an outdated firewall but it is there nonetheless. :)
-
Filehippo shows there is a free standalone version of outpost. :-\
It seems an outdated firewall but it is there nonetheless. :)
Yes there is the old stand alone version of Outpost Firewall but as you noticed yourself it's outdated and outdated software can be more problems than there worth due to incompatibilities with other software updates and windows patches, it may work for you but the risk is still there.
-
That post also states at the beginning:
If you are running Windows 7 make sure you got CIS 5.12 ( Firewall and D+ only. No AV ) to have complete control on your outbound connections...
That was the issue between Avast! and Comodo running in W7. No outbound control over program connections.
Yeah it makes sense if only I am using Comodo Firewall. I am asking about windows 7 built in firewall.
I am not referring to Comodo firewall issue at all.
-
So has this problem been fixed with the release of Comodo 5.12 ?
Can I get a confirmation from someone running Avast! Free Antivirus 7 on Windows 7 with Comodo Firewall Free, that Comodo is able to detect programs trying to connect to the internet ?
-
So has this problem been fixed with the release of Comodo 5.12 ?
Can I get a confirmation from someone running Avast! Free Antivirus 7 on Windows 7 with Comodo Firewall Free, that Comodo is able to detect programs trying to connect to the internet ?
I think you would need to install Comodo firewall 6, avast 8 is also now the current release.
-
For various reasons, I have to stay on Avast 7 for now (actually I'm still running the last version of Avast 6 because of this issue with the Comodo firewall).
And Comodo's last version is still 5.12.
-
For various reasons, I have to stay on Avast 7 for now (actually I'm still running the last version of Avast 6 because of this issue with the Comodo firewall).
And Comodo's last version is still 5.12.
You can find the latest version 6 here http://www.filehippo.com/download_comodo/tech/
-
I must be missing something, my Comodo Firewall 5.12 says it's up to date.
I'm using Comodo Firewall Free, not CIS.
-
I must be missing something, my Comodo Firewall 5.12 says it's up to date.
I'm using Comodo Firewall Free, not CIS.
comodo firewall 6
remembering that the installer is universal 32 and 64 bit
http://www.comodo.com/home/internet-security/firewall.php
comodo firewall 5.12
http://personalfirewall.comodo.com/free-download.html
windows 7,vista,xp sp2
http://downloads.comodo.com/cis/download/installs/2000/standalone/cfw_installer_x86.exe
http://downloads.comodo.com/cis/download/installs/2000/standalone/cfw_installer_x64.exe
-
Thank you everybody for the download links, but that's not what I asked for.
I just asked a simple question: Avast 7 + Comodo Free Firewall (not CIS) 5.12 + Windows 7 , is the bug still present ?
-
Ok, I finally figured it out with Comodo's naming scheme, versioning scheme, etc.
So let me update my question:
Avast 7 (last release) + Comodo 6 on Windows 7, is the bug still present ?
-
Avast 7 (last release) + Comodo 6 on Windows 7, is the bug still present ?
No.
-
Avast 7 (last release) + Comodo 6 on Windows 7, is the bug still present ?
No.
Thank you for the confirmation.
-
You're welcome.
-
I'm using Avast 8 and Comodo 5 under Windows 7, I put a block on IE9 with Comodo (I stick to Chrome these days)
Oddly I found that Google works and brings up results, however attempting to follow any of the Links is blocked by Comodo.
Unless as I had Chrome open The Google search was able to get out via this??
-
Here's the comodo log
-
Update to CIS 6.x
-
Since when and who fixed this issue? Did Avast fix this issue already? It did not only affect Comodo Firewall but also Windows one as well.
Egemen the head developer of CIS:
"The issue is avast intercepts WEB connections at the driver level and redirects connections to its own local proxy.
Because CIS operates at NDIS layer i.e. the lowest layer of the protection, it sees the actual connection i.e. avast proxy. Normally CIS should have blocked the loppback area connection to the proxy however because of the limitations in Windows 7, it fails.
CIS uses TDI, WFP and NDIS to provide its firewall functionality. WFP maybe enough ti implement an average firewall but it is not enough for a firewall like CFW so that it could not be used alone wihtout the support of the other 2 technologies. Windows 8 allowed us to use WFP more than previous windows editions and it should not be a problem with the next CIS editions which support Windows 8."
So Windows 8 is the only OS which don't seem to have this issue. Windows 7 is still not fixed.
-
Asyn: Not sure if you were referring to my Post, but Comodo 6 seems to have a number of issues with CIS forum members, mostly related to Dumming down of the interface.
My copy of V5 is not picking up on any updates, so I have decided to stick with it for the time being.
V6 is dues an update any day now (should have been at the end of the month but it is late ??) I also want to see what effect this has?
But I guess I will update soon.
-
Avast 7 (last release) + Comodo 6 on Windows 7, is the bug still present ?
No.
Any proof of this please.? ;D
-
Avast 7 (last release) + Comodo 6 on Windows 7, is the bug still present ?
No.
Any proof of this please.? ;D
Test it. ;)
-
okay.
Well im running avast 8 and comodo firewall 5.12 and i can confirm there is no issue between both programs. 8)
-
okay.
Well im running avast 8 and comodo firewall 5.12 and i can confirm there is no issue between both programs. 8)
There are other threads showing people (like me) are having problems with Comodo 6 and Avast 8.
-
I use the latest beta build of Avast Pro Antivirus and the latest stable build of Comodo Firewall with Defense+. I haven't done any exclusions. But both programs are now running fine without any issues like before. :)
-
okay.
Well im running avast 8 and comodo firewall 5.12 and i can confirm there is no issue between both programs. 8)
There are other threads showing people (like me) are having problems with Comodo 6 and Avast 8.
Im not using v6.
head over to the comodo forum and there are still plenty of problems with it.
-
Hello
I am new to this issue
but what I understand and see myself is
that Comodo Firewall V6 (as V5 did) can not manage (allow block ask) any traffic that runs through Avast's Network shield right?
I noticed I can block all this with Comodo Firewall if I apply a global rule that blocks any 127.0.0.1 (may be port: 12080 is needed) traffic.
Worse, I noticed the same accounts for little software called Proxifier! This is a legal nice and cool software I bought but! I can not controll its traffic, too, for the same reasons. SO ANY PROGRAMMER can write some piece of shitty code that uses this local proxy tunnel function and bypasses COMODO Firewall!
Avast's netshield is there no help since it can never be as good as an experienced user that controlls in/outbound traffic via firewall manually.
-
I remember when this issue was first brought to the surface and users could not block firefox from connecting.
Well i have tested this theory myself and i can confirm that comodo does block outbound connections when avast is run in tandem.
Anyway the subject is moot because avast has a primary function of preventing malware from being installed so illegitimate connections should not be an issue and if any user feels there is a need to block any connections then those programs really should not be installed on the computer.
-
Comodo Firewall v6.2.282872 has avast on its "in program" whitelist. CFW v6.2 and avast plays well together.
I have never experienced any issues. It's the CFW "behavior blocker" which creates the issue.
If you disable the CFW behavior blocker you will be fine.
CFW GUI>Tasks>Advanced Tasks>Defense+>HIPS>HIPS Settings>Behavior Blocker>untick the box and disable the Behavior Blocker. :)
Stand alone Comodo Firewall http://download.comodo.com/cis/download/installs/2000/standalone/cfw_installer.exe
To install untick everything on first screen>click "custom install">untick everything "except" the firewall>click "back"> click "agree and install" 8)
-
There are still quite a lot of issues between Win8 and CFW still to be worked out. :)
-
i am using comodo internet security premium version 6.2. but i want to give a try avast 8 latest version with my comodo firewall version 6.2. can i use that .
is there any settings i need to change for this? 8)
-
Pradon me
but I have Comodo 6.2 and Avast beta and malicious test code can go out through Avast netshield virtual network adapter / local tunner proxy what ever technique and Comodo want pop in despite tight settings in Comodo: