Comodo Firewall and Avast 7

[Guest]

[kail]

We want some answers from comodo's developers, they can't ignore this problem.

Where you getting the cited quotations from here? From Avast's forum? I don't remember Comodo saying anything in regards to this issue. The last I heard was that they were still investigating this issue.

And.. who is "we" exactly?

[paroh]

I also having the same problem Avast free version WEB shield problem with comodo firewall.

[tbmaster]

Where you getting the cited quotations from here? From Avast's forum? I don't remember Comodo saying anything in regards to this issue. The last I heard was that they were still investigating this issue.

And.. who is "we" exactly?

"We" users of comodo's firewall.

I was getting this cited quotation from comodo's forum

Recurring problems that are difficult for Comodo to permanently fix
CIS under Win 7 cannot prevent firewall connections when Avast 7 webshield is enabled.

Exactly from here

EDIT:
I have a lot of clients that use CIS, if the developers can't or don't want to solve this problem I have to uninstall it from thousands of computers. That's why an answer is needed.

[kail]

I was getting this cited quotation from comodo's forumExactly from here

Ah, from mouse1's "Known issues" topic. I think your citation is out of context here, you've missed something..

..Issues are included if I believe they represent a significant problem to users - developers may not regard all the issues below as bugs. .. Issues listed above should not therefore be regarded as confirmed current bugs by Comodo.

mouse1 is trying to get these issues noticed and fixed by Comodo. It's probably best not to cite them out of context, that will not help.

EDIT:
I have a lot of clients that use CIS, if the developers can't or don't want to solve this problem I have to uninstall it from thousands of computers. That's why an answer is needed.

I see. What have Microsoft said? That answer might prove critical to this issue .. Hang on.. if you have a +1k clients, why did you discount the W7 Firewall report earlier? Even if you only had half that amount of licenses Microsoft would still talk to you (personally).

Let me get this right.. you've installed CIS 5.8/5.9 and Avast 7 (free?) on +1,000 (one thousand.. more?) client systems?

[tbmaster]

Ah, from mouse1's "Known issues" topic. I think your citation is out of context here, you've missed something..mouse1 is trying to get these issues noticed and fixed by Comodo. It's probably best not to cite them out of context, that will not help.
I see. What have Microsoft said? That answer might prove critical to this issue .. Hang on.. if you have a +1k clients, why did you discount the W7 Firewall report earlier? Even if you only had half that amount of licenses Microsoft would still talk to you (personally).

Let me get this right.. you've installed CIS 5.8/5.9 and Avast 7 (free?) on +1,000 (one thousand.. more?) client systems?

That's not exactly as you say, I don't own the licenses personally, however why have i to ask to microsoft?
The problem is comodo's firewall, I can install any other firewall to replace it.
I never suggest the use of microsoft firewall to my clients.
With clients I mean people, i'm sorry but i'm not english so there could be some misunderstandings.

EDIT
Maybe the right term is customers not clients

[kail]

That's not exactly as you say, I don't own the licenses personally, however why have i to ask to microsoft?

Bottom line (my perspective, I've no idea what Comodo think on this) .. firstly it doesn't really matter about any third party firewall (CIS included). The fact is that Avast 7 doesn't work properly with the Windows 7 Firewall. Despite your assertions to the contrary, W7 firewall is a sophisticated modern firewall that is used by the majority of W7 users (both personal & commercial). Either Avast or Microsoft will have to fix this.. I suspect that it will fall to Avast.

I don't know why the Avast Dev's are saying they've done everything right and that it isn't their problem.. if it was just CIS, then OK (maybe). But, with the W7's firewall? I don't think so. Mind you, all this (W7 firewall specifically) should have been uncovered during Avast's testing. So, I'm not exactly sure why we are here anyway.. unless Avast 7 is acting as designed with regards to the W7 firewall.

EDIT
Maybe the right term is customers not clients

Not really, they're the same thing.

[tbmaster]

all the other firewalls don't have problems with avast and don't have this security hole...

Avast devs say this is a comodo's bug (And maybe windows firewall too).
I know something about security (I'm a developer too) and I agree with avast devs.

unless Avast 7 is acting as designed with regards to the W7 firewall

I don't think malwares act as designed with regards to the W7 firewall.

However I'll test personally w7 firewall without comodo and I'll let you know.

[kail]

all the other firewalls don't have problems with avast and don't have this security hole...

Avast devs say this is a comodo's bug (And maybe windows firewall too).
I know something about security (I'm a developer too) and I agree with avast devs. ..

Seriously? For you this should be irrelevant. If Avast 7 is indeed breaking/circumventing (accidentally or otherwise) W7's firewall, then Avast should have reported this to MS when they first realised it (and that should have been before they released it!). Anything else would be.. well.. irresponsible.

You know about security and you're a developer.. and yet you agree with the the Avast Dev's? That is, you agree that it is a bug in CIS? This makes me doubt your personal claims here. CIS would be the least of your concerns/worries unless your firewall recommendation was a mandatory one that you had verified the compliance of. But, then it wouldn't be a recommendation at all.. would it?

.. However I'll test personally w7 firewall without comodo and I'll let you know.

This doesn't help either. With "thousands" of client/customer/whatever on the line, you're only doing this now? Unbelievable.

edit: On thinking about this, I'm having a great deal trouble believing that the Avast Devs actually know about this issue with Avast 7 and W7's firewall. I can believe that they might act this way with regards to CIS or another 3rd party vendor (unfriendly as that might be).. but, W7's firewall? I'm finding this very difficult to believe.

[Radaghast]

Perhaps it's just my imagination, but it looks to me like Private Firewall is doing a pretty good job of NOT being able to block these connections. However, in fairness, I'm not totally conversant with the product, so I'd have to see if there are any other options available for blocking the connection.

[aerofly]

kail
In my opinion you are missing a point.
What about if i write an hidden proxy like avast 7 ( maybe i can reverse engineering their driver or whatelse) and use it to phone home?
I will bypass Comodo firewall and W7 firewall and nobody can blame avast.
In my opinion they have casually discovered a security hole that affect some firewall and some not.
I think this should be seriously investigated instead that denied.
On the other hand i agree with you that avast should have notified microsoft and/or Comodo (if avast was aware of that issue before releasing version 7)

[kail]

.. I think this should be seriously investigated instead that denied. ..

Please don't misunderstand, to the best of my knowledge Comodo are investigating this issue.

My posts here are not some sort of ruse the deflect this issue away from CIS either. Whatever Comodo is doing, thinking or looking at with regards to this issue is completely independent of me and what I've posted here.

[tbmaster]

kail...

I agree with aerofly, you're trying to deny a problem here attacking me.

Personally I don't care about W7 firewall because I'll never use it as my primary firewall.
And if it is so good as you say than I don't see the need for third party firewalls to exist.

Radaghast I 've said that private firewall is working good based on testing of avast users in avast's forum, but I don't have tested this personally.

EDIT
Radaghast I've seen the picture you posted, Try selecting the boxes under IP addresses in the rules...

[Radaghast]

kail...

...Radaghast I 've said that private firewall is working good based on testing of avast users in avast's forum, but I don't have tested this personally.

If you're referring to the comment by craigb, it's worth pointing out that he also said'

Its' also just the outbound protection of the windows firewall that causes some problems but in it's default state it works fine.

It's the inability of the firewall, to prevent certain outbound connections, when use in conjunction with the Avast Web-Shield, that's the problem. Unfortunately, Windows firewall, along with CIS, PersonalFirewall and at least one other are not able to do this.

As far as PersonalFirewall is concerned, I think the image speaks for itself, but you're welcome to test it.

[kail]

kail...

I agree with aerofly, you're trying to deny a problem here attacking me.

Personally I don't care about W7 firewall because I'll never use it as my primary firewall.
And if it is so good as you say than I don't see the need for third party firewalls to exist. ..

It's not about you, it never was. It's about the majority of W7 users that you don't care about. My only "attack" on you (if it could be called that) was me saying that I didn't believe what your were saying.. and I think your post fully supports my skepticism. You say the above.. and yet you also claim that you represent "thousands" of end users? Contradict yourself much? Looks like you're trolling to me. Sorry, I'm done with you.

[Radaghast]

...EDIT
Radaghast I've seen the picture you posted, Try selecting the boxes under IP addresses in the rules...

They are simply for blocking sites or IP addresses. If I use the rules shown in the image, without Avast being installed or with the Web-Shield disabled, firefox is blocked. if I enable the Web-shield, firefox connects. This is the same behaviour seen in the other firewalls.

[Tags:]