Queued alerts still appear after rules have been manually created [M648]

A. THE BUG/ISSUE (Varies from issue to issue)
[ol]- Summary - Give a clear summary in the topic subject, NOT here.

  • Can U reproduce the problem & if so how reliably?: Yes, fairly reliably.
  • If U can, exact steps to reproduce. If not, exactly what U did & what happened: While reproducing works with most programs I find it fairly easy to replicate with a torrent client.
    a: Download a torrent client, portable works well (I used tixati portable) Start the client but don’t answer the firewall alerts.
    b: Add a new torrent to the torrent client, for example Ubuntu but don’t answer the firewall alerts.
    c: Go into the advanced settings and create a firewall application rule for the torrent client that says to block IP in and out from any to any with any protocol.
    d: Untick the “Remember my answer” in the firewall alert and then click Block > Block only
    e: You will now continue to get these alerts that are queued, Block and Terminate doesn’t help, queued alerts will still come.
  • If not obvious, what U expected to happen: I expected the queued alerts that now had rules to be disregarded.
  • If a software compatibility problem have U tried the conflict FAQ?: I don’t believe there is a software compatibility problem.
  • Any software except CIS/OS involved? If so - name, & exact version: Tixati portable v1.96
  • Any other information, eg your guess at the cause, how U tried to fix it etc: My guess is that queued alerts simply don’t respect rules created after the alert was queued, it would make sense.
    I tried to fix it by killing tixati, had no effect, but rebooting seems to fix it as I suppose it flushes the queued alerts.
    Further elaboration can be found here.
    [/ol]

B. YOUR SETUP (Likely the same for each issue, so you can copy forward)
[ol]- Exact CIS version & configuration: 6.3.294583.2937 - Configuration file attached.

  • Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV: HIPS - Safe Mode, Autosandbox - Disabled, Firewall - Custom Ruleset, AV - Stateful.
  • Have U made any other changes to the default config? (egs here.): Configuration file attached.
  • Have U updated (without uninstall) from a CIS 5?: No
    [li]if so, have U tried a a clean reinstall - if not please do?: N/A
    [/li]- Have U imported a config from a previous version of CIS: Yes
    [li]if so, have U tried a standard config - if not please do: Yes, same issue.
    [/li]- OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used: Windows 8 64bit, UAC disabled through registry, Administrator account, real system (not a virtual machine)
  • Other security/s’box software a) currently installed b) installed since OS: a= Zemana AntiLogger Free b= Zemana AntiLogger (paid)
    [/ol]

[attachment deleted by admin]

I’m a little bit confused. Do you mean that there are already a few popups on the screen when the rule is created, and that after that the popups remain?

Is that what you’re saying, or are you saying that even after creating the rule which should negate the need for the popups the popups keep coming for a while? Please clarify as I can’t quite visualize this yet?

Thanks.

Neither of what you said, in CIS 6 only one alert will show at one time and the rest are queued until you’ve made a decision on the current alert. It’s the queued alerts that still show up even if you manually create a rule that deals with them, so I had to either a) click through thousands of alerts or b) restart … I chose b.

  • So lets say you have a program called example.exe that tries to connect to 1.1.1.1, 2.2.2.2, 3.3.3.3, 4.4.4.4, 5.5.5.5 and 6.6.6.6 at the same time.
  • Now you’ll get a firewall alert for example.exe which says it tries to access 1.1.1.1 however the alerts for 2.2.2.2, 3.3.3.3, 4.4.4.4, 5.5.5.5 and 6.6.6.6 are queued but not showing on the screen currently.
  • Now while still at the alert for 1.1.1.1 you go into the advanced settings and create a firewall rule that says to block all traffic for example.exe and you apply it.
  • Now for the firewall alert of 1.1.1.1 you un-check “Remember my decision” (not needed but to keep the application rule clean) and then block only.
  • Now firewall alerts for 2.2.2.2, 3.3.3.3, 4.4.4.4, 5.5.5.5 and 6.6.6.6 will come one after the other… even though you have a rule that takes care of the queued alerts.
  • Now imagine a program like a torrent client that tries to connect to thousands of people… yeah not a fun time.

You can read more in my help thread found here or my wish found here.

Okay, now I understand. I apologize for apparently forgetting how CIS works. :embarassed: I’ll forward this to the devs.

Thank you very much for your report in standard format, with all information supplied. The care you have taken is much appreciated by Comodo, and will increase the likelihood that this bug can be fixed.

Developers may or may not communicate with you in the forum or by PM/IM, depending on time availability and need. Because you have supplied complete information they may be able to replicate and fix the bug without doing so.

Many thanks again.

Doesn’t seem fixed in CIS version 6.3.302093.2976

Thanks for checking this.

I’ve updated the tracker.

Not fixed in CIS 7.0.308911.4080 Beta. (Started application and got pop up, opened CIS and made rules to allow certain things and block everything else and clicked OK, still getting hundreds of alerts for things that the rules should deal with)

Thank you for checking this. I’ve updated the tracker.

Can you please check and see if this is fixed with the newest version (7.0.313494.4115)? Please respond to this topic letting us know whether it is fixed or if you are still experiencing the problem.

Thank you.

PM sent.

As can be seen in this video Warning Warning Warning Warning Warning Warning Warning Warning Warning - YouTube (When it finishes uploading and processing) it is not fixed in CIS 7.0.313494.4115

Thank you for checking this. I have updated the tracker.

Not fixed in 7.0.317799.4142

Thank you for checking this. I have updated the tracker.

The devs have not marked this as Fixed in the tracker. However, sometimes bugs are fixed by the release of new versions, but not marked as Fixed in the tracker.

If you are able please check with the newest version (CIS version 8.0.0.4337) and let me know if this is fixed on your computer with that version.

Thank you.

I can’t at the moment and I’ll probably forget later, please send me a PM so I won’t forget. =)

PM sent.

This issue has not been fixed in CIS 8.0.4337

Thanks for checking this. I’ve updated the tracker.

Hello,

The devs have not marked this as Fixed in the tracker. However, sometimes bugs are fixed by the release of new versions, but not marked as Fixed in the tracker.

If you are able please check with the newest version (CIS version 8.1.0.4426) and let me know if this is fixed on your computer with that version.

Thank you.

Not fixed in 8.2.0.4508