List of current bugs discussion

just to end this endless questions: https://forums.comodo.com/news-announcements-feedback-cis/questions-regarding-development-of-cis-t127440.90.html

ming said he is working on a new release.

he didnt say its related to cis free but its something, right?

lets see… i have printed it. lets wait until january to see if something happens and if so, what will be the release notes for it…

im going quiet mode for now and wait for something to happen…

https://forums.comodo.com/install-setup-configuration-help-cis/large-cmddata-file-t120322.0.html;msg864460#msg864460
Hi all,

Could everyone please confirm that the cmddata file increases in the CIS v12.2.2.8012 or not ? as we couldn’t see large size of cmddata in our machines.

Thanks
C.O.M.O.D.O RT

V12.2.2.8012 (Firewall only) Windows 7 Ultimate 64-bit (clean install with all MS-updates)

cmddata size = 96Mb and stable. :-TU

Nothing dramatic on Win10 & 11 systems here. 96MB on most. One Desktop has 100MB . . . . none have changed

W10 Famille - 20H2 - 19042.1348/ CIS PRO : 12.2.2.8012
cmddata size : 669 MB; stable now

W10 Famille - 21H1 - 19043.1348 / CFW : 12.2.2.8012
cmddata size : 196 MB; stable now
Update : on 03 August 2021 the cmddata size was 98 MB
https://forums.comodo.com/install-setup-configuration-help-cis/large-cmddata-file-t120322.0.html;msg909910#msg909910
the size has therefore doubled since that date

Mine is 192 MB
Win 10 LTSC 1909

I recall vaguely that when I first fresh installed this latest version of CIS, the file was in the 90s of MB, but I am not too sure of my memory.

Hello,
I would like to know how much time devs are dedicating to fix these issues.
I don’t want to be rude but i would like to pay for a good firewall solution, often updated with fast bug fixes.

Is the comodo team working on this stuff? What are the company goals for the future? When will a new version be out?

Thank you

Can you add this to the list : HIPS Protected Objects read-only access not working

It’s a long standing issue.

Thank you.

No because it is not an issue, what you are suggesting is to completely undo safe mode to the point where safe mode would become useless. For the last time, if you do not want trusted applications to be able to modify files that are set in protected files, you must set HIPS to paranoid mode. Safe mode is not going to prevent or alert about trusted applications from doing anything other than when they try to execute an unknown or malicious rated executable.

As I discovered lately (see the relevant thread) HIPS Safe mode can be setup in such a way so that it is possible to create read-only access protection for selected files and/or directories, perhaps you gave it a try and can confirm that it works.

If I can intrude on this thread, I’d just like to point out that the exceptional protection afforded by Comodo rests in the Containment + Firewall combination. In spite of the resources put into the AV segment, an honest opinion would be that it is mid-tier at best. And some secret knowledge here: ANY HIPS modules can be bypassed quite easily (trust me), even those that are set at the “paranoid” level.

This being said, Best Practice would be to streamline a Comodo setup and not play st all with settings that add nothing to protection but can potentially lead to annoyances. Remember that the amount of bugs seen is directly proportional to the complexity of the setup one uses.

Keep it simple and be happy.

hi sis…

lets consider this: cis free is not abandoned and they release a new edition fixing the problems regardles cis modules taking high cpu and ram, and cis ignoring already trusted files… lets say they release a new update fixing these things… now i ask you my girl: is that possible to have full cis (with av, just to lets defender diabled) but making windows not check for updates status on the av active?

check this case: before cis becomes this horrendus thing, i used it with all on (av, fw and sandbox) and i marked the db updates to be done from 29 to 29 days (dont remember correctly but i marked the high aplicable time accepted by cis) and even so windows check for updates and always showed notificaton regardless this. so i ask you, as you may have the acnowledge, is that possible to make cis av module only check for updates from 6 to 6 months and make windows not check it? if so, and if comodo solve these bugs, it would be my “welcomeback cis” again…

I’m at 237MB on .8012. Last time I checked I think it was under 100MB maybe a few weeks ago.

The list of current bugs is expanding, but no status indication (i.e. resolved / in progress / to be done / will not be fixed / etc.) is given on any bugs on the list.

  1. Yes, HIPS alerting file/directory creation by (unknown) applications did work in older CIS versions. Bug fix should be set to high priority as it is a security issue.
30. HIPS ignores certain actions of applications that are running as the SYSTEM account. E.g. Direct disk, direct keyboard, direct monitor access. That means if an unrecognized application is elevated to SYSTEM, HIPS will not alert for various actions carried out by that unrecognized application.
Hi all,

From the above reported issue no-30, we understood that when the unrecognized application is elevated and running, the HIPS is not alerting for various actions carried out by the unrecognized application right
Or did we missed something to understand about the issue ?
If anyone could able to elaborate this issue detailly, please elaborate so that we will report this to the team.

Thanks
C.O.M.O.D.O RT

I confirm the issue.
If I run an unrecognized application elevated to SYSTEM then HIPS doesn’t alert for Direct disk access. However when the same unrecognized application is run as administrator then HIPS does alert for Direct disk access.
Same issue might happen with direct keyboard, direct monitor or other access methods, I did not check that.

Hello all,
I did the test and everything works fine for me under:
Windows 10 Pro x64 Build 19043.1348 - Comodo CIS Pro v.12.2.2.8012
Custom firewall mode
Safe HIPS mode

In addition to bug no. 30.

When executing another unrecognized application with Administrator credentials the following HIPS Alerts appear:

  • Two Alerts that application is trying to access a protected COM interface.
  • One Alert that application is trying to access the disk directly (Direct disk access).

When executing the same unrecognized application as above but now with SYSTEM credentials the following HIPS Alerts appear:

  • No alerts at all.

A severe security issue if you ask me.

You’d better provide the sample and step-by-step to help the staffs easily reproduce the issue.