TOPIC TITLE
Functional Bug: Firewall doesn’t take into account changes to File Groups
A. THE BUG/ISSUE:
1. What you did: Added an application to a File Group used in a Firewall Application Rule which treated the File Group as “Blocked Applications”.
2. What actually happened or you actually saw: The added application could still access the Internet. Restarting COMODO Firewall would make the changes to take effect and block the added application.
3. What you expected to happen or see: The changes to File Groups should take effect immediately. Added/removed applications must be taken into account right away.
4. How you tried to fix it & what happened: See 7.
- If a software compatibility problem have you tried the compatibility fixes (link in format)?: N/A
- Details & exact version of any software (except CIS) involved (with download link unless malware): N/A
7. Whether you can make the problem happen again, and if so precise steps to make it happen:
a) Define a new File Group (i.e. named “Blocked Applications”) and add applications (i.e. Firefox, Internet Explorer…) to the group.
b) Add a new Firewall Application Rule, select the new File Group above, use the predefined network access policy “Blocked Application.” Move the new Application Rule up to the top of the list. It doesn’t matter whether Firefox and IE are already included in other application rules. Click OK.
c) Run Firefox / Internet Explorer and try to open any Web Site (i.e. Comodo, Google…) => they still can access the Internet.
d) Exit COMODO Firewall and restart it. Retry c), both Firefox and IE are now blocked.
e) Remove Firefox from the File Group defined in a), click Apply, OK…
- Retry c), Firefox is still blocked.
- Using the tray icon context menu, switch the Firewall Security Level to Disabled, then switch back to the previous level. Retry c), Firefox is still blocked.
- Export the configuration and re-import the same configuration. Retry c), Firefox is still blocked. Click Activate to reactivate the configuration => Firefox is now unblocked.
8. Any other information (eg your guess regarding the cause, with reasons): In terms of programming, I guess the developer just needs to add code so that COMODO Firewall will reload the Firewall settings after changes are made to File Groups.
B. FILES APPENDED. (Please zip unless screenshots).:
- Screenshots of the Defense plus Active Processes List (Required for all issues): iirelevant as this bug is within COMODO Firewall itself and it’s easy to reproduce it.
- Screenshots illustrating the bug:
- Screenshots of related CIS event logs:
- A CIS config report or file:
- Crash or freeze dump file:
- Screenshot of More~About page. Can be used instead of typed product and AV database version:
C. YOUR SETUP:
1. CIS version, AV database version & configuration:
COMODO Firewall 5.10.228257.2253
2. a) Have you updated (without uninstall) from a previous version of CIS: No.
3. a) Have you imported a config from a previous version of CIS: No.
4. Have you made any other major changes to the default config? (eg ticked ‘block all unknown requests’, other egs here.): No.
5. Defense+, Sandbox, Firewall & AV security levels:
Defense+ = Safe Mode
Sandbox = Enabled
Firewall = Custom Policy
AV = N/A
6. OS version, service pack, number of bits, UAC setting, & account type:
Windows 7 Home SP1 64-bit
UAC = Always Notify
account type = Administrators
7. Other security and utility software currently installed: None.
8. Other security software previously installed at any time since Windows was last installed: Zone Alarm Free 2012.