Renaming a portset breaks rules & GUI [M232]

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

  • Can U reproduce the problem & if so how reliably?: yes, 100%
  • If U can, exact steps to reproduce. If not, exactly what U did & what happened:

It looks like renaming a portset does not update rules.

  1. Create a new portset - for example “test”.
  2. Add any port - for example “12345” - optional step.
  3. Create an application rule or global rule using this port (source or destination).
  4. Click OK to close advanced settings - optional step, to be sure that config is updated (however in 6.0 it looks like changes are live, in 5.x we had to save config to use new portset/netzone)
  5. Reopen settings and change our portset name to for example “test2”.
  6. Click OK to close advanced settings - optional step.
  7. Check our rule. It’s title still says “test”, however inside it uses name for the first portset in our list (for me it’s “HTTP”). When we export config before and after renaming we see that rules were not updated.

Please note that renaming a network zone updates all rules using it.

  • If not obvious, what U expected to happen: rules should be auto-updated
  • If a software compatibility problem have U tried the conflict FAQ?:
  • Any software except CIS/OS involved? If so - name, & exact version:
  • Any other information, eg your guess at the cause, how U tried to fix it etc:

I have attached portions of my configs before and after renaming. Note that I used here names “test-ps” and “test-nz” to validate if netzones are also afflicted (they are not).

  • Always attach - Diagnostics file, Killswitch processes list, dump (if freeze/crash). If complex - CIS logs & config, screenshots, video, zipped program (not m’ware)
    [/ol]

B. YOUR SETUP (Likely the same for each issue, so you can copy forward)
[ol]- CIS version & configuration: 6.0.260739.2674, own config

  • Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV: all
  • Have U made any other changes to the default config? (egs here.): sure
  • Have U updated (without uninstall) from a previous version of CIS: no
    [li]if so, have U tried a a clean reinstall - if not please do?: no
    [/li]- Have U imported a config from a previous version of CIS: no
    [li]if so, have U tried a standard config - if not please do: no
    [/li]- OS version, SP, 32/64 bit, UAC setting, account type, & VM used: XP Pro, SP3, 32b, admin
  • Other security/sandbox software a) currently installed b) installed since OS: none
    [/ol]

Logs attached, PM for pwd.

[attachment deleted by admin]

I can confirm this but it’s also something that hasn’t worked for a while. When I looked at this, zones and port set renaming doesn’t feed through to firewall rules automatically.

Well, it worked in 5.12 fine. Also keep in mind that renaming netzones updates rules without problem. This is obvious bug crippling rules (rule shows wrong ruleset, also rule is not executed, because there is no longer such portset - renaming default “HTTP Ports” to “HTTP” I’ve broke “Web Browser” ruleset).

I never used 5.12 as there were several network problems with that version. In 5.10, port set name changes were never a problem but zone name changes were. In the image below the zone is now called LAN, yet the rules for the System process and corresponding Global rules, still have it as Home#1. This is also reflected in the exported configuration file. It certainly used to work, but I’d have to try the earlier versions to ascertain which.

[attachment deleted by admin]

OK, let’s say 5.x. About portset/netzones you had to close a config after renaming to save it, otherwise dialog still used previous names (updates were made after you click “ok” - if I remember correctly this was one of my bug reports).

PM sent

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 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

Mouse

2708 - not fixed

Tracker updated

2801 - not fixed

Thanks very much, tracker updated

Can you please check and see if this is fixed with the newest version? Please let us know whether it is fixed or you are still experiencing the problem.

Thank you.

PM sent.

2847 - not fixed (still after renaming a portset app rule uses its old name and while editing it GUI shows first portset instead - “HTTP Ports”)

Thank you for checking this.

I have updated the tracker.

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

Thank you.

PM sent.

2937 - confirmed as still not fixed. This is weird as a similar bug report about renaming rulesets was fixed some time ago (for network zones there was never such bug - renaming zones makes automatic changes in rules).

Thank you for checking this.

I have 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.

Hi wilk,

Devs have marked this issue as “Fixed”. Please verify.

Thanks.

The devs have marked this as Fixed. I will therefore move this to Resolved.

If you find that this is not fixed on your computer please follow this through in the tracker.

Thanks.