Yep!
it’s only of lesser significance because most people don’t configure MS FW for outbound filtering?
Another firewall (such as the Windows 7 firewall) having limitations doesn’t by definition justify limitations in Comodo firewall. Although it is theoretically possible that the other firewall has similar limitations due to limitations in the OS itself, it is also theoretically possible that isn’t the reason for there being a similar limitation.
I never said it did. However, it certainly does make a nonsense of some posts when they are aimed solely at CIS. Besides, my main concern with this issue (see my previous posts) is that the majority of users on W7 are probably just using W7’s Firewall with one of these web proxies and thinking that they are fully protected.
Some may wish to call that a limitation, but at this point I’d prefer to call that an unmitigated disaster myself.
This being a Comodo forum, I would normally expect comments to focus exclusively on Comodo firewall. Even in cases where the user is well aware that other firewalls have similar limitations. So I wouldn’t let that get to you.
Hopefully, those Windows 7 firewall users who are aware of the issue are in Windows 7 forums trying to get a proper response from Microsoft.
The masses who aren’t even aware of the issue, well, I’m not sure what you do about them. I suppose someone so inclined could start contacting media outlets, trying to get them to cover the subject.
From what egemen has said, my understanding is that the problem is inside win7. Hence the solution should come from Microsoft either through a patch or an SP2, but egemen doesn’t think that to be needed and that a workaround would be enough.
Quote from egemen
It may not be necessary. For this particular issue, we may have a workaround. We are looking into it.
He was of course referring to the problem with Avast 7, but is it really the sole problem than the “limitations” of win 7 could yield?
Where is that quote from Boris 3? If a public post, I’d like to find the full message and read the rest of it.
My apologies, I assumed that you had read this topic. However, I’m not aware of any other firewalls that have this issue currently. Do you know otherwise?
Also is there a significance to your use of “limitation” here… do you believe it is a limitation of some sort?
You can find it here : https://forums.comodo.com/beta-corner-cis/cis-beta-for-windows-8-customer-preview-t83044.0.html;msg592815#msg592815
Thanks Boris 3. I saw that one, but either missed or forgot about the one which was a few posts later in that Windows 8ish thread:
Have you looked at the default settings for CIS recently.
As far as I recall, WFP was introduced in 2008, which I think was Vista SP1 and Server 2008. I did run a test on Vista and the issue wasn’t apparent.
Rereading that "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." comment, I think there are two interpretations:
- Future versions of Comodo which support Windows 8 should fix the “avast7 type redirection issue” even when running on earlier WFP platforms such as Windows 7.
- Future versions of Comodo will only fix the “avast7 type redirection issue” when running on Windows 8 or later.
The beta version of CIS for Windows 8 doesn’t have this problem and I think it likely the current version will be patched to ‘fix’ the issue.
I have seen some signs that there may be OS version specific differences in WFP.
There are. The most recent update for Windows 8, has a number of significant new features.
I've yet to see it substantiated that the avast7 WebShield functionality is using some WFP feature that is OS specific. I've also yet to see it substantiated that a firewall needs an OS version specific WFP feature in order to cope with the avast7 type redirection issue. Should anyone be able to provide details on such subjects, I for one would enjoy reading them.
According to the Avast developer, in the Avast forum thread, they changed their driver in Avast 7 from the TDI API to WFP and it may well be this that’s causing the problems, with CIS and some other third-party firewalls, running on Windows 7. The problem, as it affects users of Windows own firewall, on either Windows 7 or 8, is slightly different, as both Avast web-shield and Avira web-guard allow applications to bypass the firewall regardless of the settings for the individual applications.
I assume that means when it is running on Windows 8. Can it also be run on Windows 7? If yes, does it also fix this problem on Windows 7?
The beta version referenced only runs under Windows 8. The current version will need to be patched. This is something egemen has hinted at. (The link was given a posts above)
OK, thanks for reply. Given the name I was inclined to think that but wanted to be sure.
No, but I am aware of the default setting change.
Let me expand (it was 4am here).
it’s only of lesser significance because most people don’t expect or configure MS FW to filter outbound connections.
On the other hand, the likely expectation of a person taking the trouble to install a 3rd party firewall, is that the product will be filtering outbound connections when configured to do so.
I’m not convinced that’s entirely true and I don’t think using the feedback from a forum like this would be representative of the majority.
I think one of the reasons people install third-party firewalls, is because they’re still under the misguided impression that it’s the same product found in XP. For those, just installing something, will give them piece of mind. That aside, even looking at the users of this forum, how may do you suppose simply use either, outgoing only or trusted as their rules of choice, assuming they’re even creating their own rules.
I get the feeling Moderators do not want this fixed.
Every-time someone asks for answers they get criticized.
Please less dismissing the issue and more resolution is needed.
How about providing an update from the dev for instance?
we want it fixed but there is nothing we can do about about it, what is driving us mad is people coming in here and making it look like the problem is only comodo while forgetting others are having the same issue and should instead be badgering MS to get this fixed, it is their problem that they introduced in Windows 7. You have had updates for the main dev, and he told you they are working on it. When we have updates we will let you all know but for the time being we don’t have anything.
Before Comodo users can petition Microsoft to do something they need to know what that something is. IOW, we’re in limbo until we get something definitive and specific from egemen or whoever. If/when we get a “OK, there is no work-around, Comodo users on Windows 7 are and will remain SOL unless Microsoft makes WFP feature XYZ available in Windows 7” (or whatever) then at least those who are willing to make an effort can describe what it is they need.