Comodo Internet Security 2020 v12.2.2.7098 Released

[C.O.M.O.D.O RT]

Hi xgiovio,

Our developers have fixed several issues. The bug fixes will be gradually included in subsequent versions. We are expecting next CIS release with in a day or twice.

[ZorKas]

Hi xgiovio,

Our developers have fixed several issues. The bug fixes will be gradually included in subsequent versions. We are expecting next CIS release with in a day or twice.

Hello,
Thank RT 
Up > Windows 10 Pro x64 Build 19042.870
No prob CIS  v12.2.2.7098
Systray > Ok

[Ploget]

Same here, with latest update to 19042.870 . . no problems at all

Hello,
Thank RT 
Up > Windows 10 Pro x64 Build 19042.870
No prob CIS  v12.2.2.7098
Systray > Ok

[Nastrahl]

Kinda unacceptable CIS updates not rolling out to address the utterly serious issue of the firewall component preventing the installation of virtual network adaptors and not allowing HYPER-V to create new virtual network adapters which is does on each reboot.

I never noticed that.

I had Application Guard enabled which creates at each reboot a virtual adapter and Comodo asks each time about the newly detected network zone (that can be disabled and set to consider all new network as trusted or something like that) without issue.

[Nastrahl]

I would like to know if this software has been abandoned.

No updates in months.

A lot of bugs not fixed.

Some example: can't filter hostname (it blocks or allows entire ranges of ip), if there are multiple requests, the popup disapper and blocks all connections, etc

Please, comodo devs, could you please take a minute to say if you are going to fix the problems?

Although the primary purpose of a firewall is to filter IPs and ports, not hosts, it always worked fine on my side. On firewall rules or website filtering after importing a customised hosts file. But I never set it to ask, only to always automatically block.

[CISfan]

I never noticed that.

...

Many other users have noticed that, unfortunately. Hence many of them went back to version 6882.

[megaherz33]

CIS 12.2.2.8012 Beta
Windows 10 21H1 19043.899 x64 Pro
No problem

[futuretech]

Do not spam this topic about the beta build, continue discussion in https://forums.comodo.com/news-announcements-feedback-cis/when-can-we-expect-a-new-version-comodo-internet-security-premium-merged-topic-t125578.0.html hence I have split and merged posts into that topic.

[prodex]

Although the primary purpose of a firewall is to filter IPs and ports, not hosts, it always worked fine on my side. On firewall rules or website filtering after importing a customised hosts file. But I never set it to ask, only to always automatically block.

 

[CISfan]

Although the primary purpose of a firewall is to filter IPs and ports, not hosts, it always worked fine on my side. On firewall rules or website filtering after importing a customised hosts file. But I never set it to ask, only to always automatically block.

CIS treats host names as a single closed consecutive range of IP addresses from low to high,
How do you manage multiple single IP addresses or multiple IP address ranges that do not belong to or fall into the host name IP addresses?
In other words, how do you manage the IP address holes of a host name and how do you know what IP addresses belong to a host name and when there is change in IP addresses used by that host name?
I'm really wondering how you take care all of this.

[domo78]

For the price it does a lot of things.

You are free and you can always go elsewhere and choose another software publisher.

That's what I do when I'm not satisfied with a provider..

[CISfan]

I think that the devs are aware of the shortcomings of a FW rule based on a host name and that they are competent enough to correct the host name implementation so that it works as everyone would expect it to work. That is, look up a host name and create/update the matching IP table and create/update the FW rule based on that host name's IP table.
But maybe this is easier said than done...

[Ploget]

That previous post has been moved to the Forum Policy Violation Board, for quite obvious reasons. Thanks CISfan for explaining the apparent Firewall failings referred to

[Citizen K]

I think that the devs are aware of the shortcomings of a FW rule based on a host name and that they are competent enough to correct the host name implementation so that it works as everyone would expect it to work. That is, look up a host name and create/update the matching IP table and create/update the FW rule based on that host name's IP table.
But maybe this is easier said than done...

This problem has been around for a decade or so. I can only assume Comodo is aware of this.

The problem boils down to the fact that hostname gets resolved to its IP address only once per Windows session iirc. That does not fly well with dynamic IP addresses which could change during the Windows session.

[Nastrahl]

CIS treats host names as a single closed consecutive range of IP addresses from low to high,
How do you manage multiple single IP addresses or multiple IP address ranges that do not belong to or fall into the host name IP addresses?
In other words, how do you manage the IP address holes of a host name and how do you know what IP addresses belong to a host name and when there is change in IP addresses used by that host name?
I'm really wondering how you take care all of this.

Maybe I haven’t actually encountered a context where it failed.

To take care of that I use a DNS server since that’s why they are made for.

A firewall isn’t supposed to manage hosts in the first place. Only IP, ports and protocols depending of their implementation levels.

But since CIS has the feature, I agree that it has to be fixed.

I think that the devs are aware of the shortcomings of a FW rule based on a host name and that they are competent enough to correct the host name implementation so that it works as everyone would expect it to work. That is, look up a host name and create/update the matching IP table and create/update the FW rule based on that host name's IP table.
But maybe this is easier said than done...

It need to build it’s own DNS database somehow, and has to block DNS requests for the given hosts in the blocklist, but also to block connection to the IPs that can be DNS reversed to the ones in the blocklist, as long as the actual DNS server doesn’t bypass all its protection he try to provide.