Comodo Firewall and Avast 7

[Guest]

[mouse1]

Indeed a curiosity. I suppose the argument is that custom applies only to firewall policies.

Note that in D+, specific CSP restrictive policies take precedence over the trusted files policy.

Precedence of autosandbox and csp policies.

Wish I had time to experiment.

Best wishes

Mouse

[clockwork]

Add a rule below your existing Application rules that blocks everything else:

Nostalgic....
Reminds me on the line interface firewall i used a long past ago

[mouse1]

Indeed it does, and here again is another curiosity. If one switches the firewall to Custom Policy mode with alerts on very high, then whatever 'trust' may have been conferred by D+, should be removed. That is, or should be, the point of Custom Policy mode.

That aside, I did delete the TVL and trusted database, along with all the other files in the database directory. After allowing the least number of D+ rules to keep Avast working, the firewall is still bypassed. 
 

Yet another curiosity - just received an inbound OpenDNS connection request to Dragon. On the alert I chose to display a full set of options, and only then selected allow.

Got an allow from Mac any to/from Mac any, Any Protocol rule. The convention used to be that you got a specific rule if you clicked on more options before allowing access? Maybe I've got this wrong as I'm not a firewall expert.

The only way I could get a specific rule was by choosing a policy....

Win 7 64 bit again ........?

[Radaghast]

I've noticed, when testing inbound connections, the resultant rule can be horribly generic, regardless of the firewall settings. I'd have to go back a few versions to see if/how this differs from the current situation.

[mouse1]

I've noticed, when testing inbound connections, the resultant rule can be horribly generic, regardless of the firewall settings. I'd have to go back a few versions to see if/how this differs from the current situation.

Difficult to see this as intentional. How does it differ from making something a (FW) trusted file? So why offer both choices?

I'm in danger of OT, so I'll moderate myself now

More on topic do we know what happens when Avast 7 Web Shield is running and a file that is sandboxed tries internet access?

Best wishes

Mouse

[tbmaster]

I've updated Comodo to the latest version 5.10.228257.2253 but the problem isn't solved.
Every blocked app can connect to the internet with Avast Shield activated.

[languy99]

I've updated Comodo to the latest version 5.10.228257.2253 but the problem isn't solved.
Every blocked app can connect to the internet with Avast Shield activated.

don't mean to sound mean but was anything in the release notes mentioned about this issue being solved?

[iroc9555]

I'm in talk with the devs so we will get to the bottom of it.

Any news you can share.

Thanks.

[hellion]

Hi All,

CIS was updated to version 5.10.228257.2253.

This Avast 7 issue is still very much a problem.

[tbmaster]

don't mean to sound mean but was anything in the release notes mentioned about this issue being solved?

Well, don't mean to sound mean but have you read the release notes?
Have you read something like:
"Compatibility with other security suites is improved in Windows 7 x64"  or
"fixed: HIPS can leak process handles with a special set of access rights"

I'm not a comodo's developer so I don't know if it regards avast but it's possible.
I've had enough to hear complaints about my posts, Comodo has a problem and as of today has not been fixed, that's the reality and no one can change it.

[aim4it]

Those sound like changes to Defense+ and not the firewall driver.

[tbmaster]

Ok, I can confirm that PrivateFirewall is not affected by this bug.

Code:

http://forum.avast.com/index.php?topic=93953.msg763494#msg763494

Comodo and windows firewall are the only ones affected by this bug.

In the known issues thread of this forum, I've read that this is a difficult bug to resolve permanently.

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

What that means? Comodo will not fix this? or they have to wait for microsoft to fix windows firewall?

A firewall that can't block connections and cannot be fixed! OMG!

[clockwork]

"CIS under Win 7 cannot prevent firewall connections when Avast 7 webshield is enabled."

Its for windows 7 only?

And why can others fix it, or even never show this behaviour then, when thats "difficult to fix"?

[tbmaster]

"CIS under Win 7 cannot prevent firewall connections when Avast 7 webshield is enabled."

Its for windows 7 only?

And why can others fix it, or even never show this behaviour then, when thats "difficult to fix"?

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

[Dumper1]

I hope this problem gets corrected soon, I will stick to Avast 6 until then.

[Tags:]