[Quote=Jay2007tech]I like the way you think. I got a few laptops, but the one laptop I use I have is setup up so its very granular with lots of hip rules. Everything is extremely well controlled. It gets the full drama treatment. (not too many hip rules or comodo will forget (its a known bug. It wont get fixed because it’ll require alot of code rewrite and it only affects less then 1% of comodo users because most people dont write an extreme amount of hip rules)
[/quote]
For now, you can bypass worrying about these glitch, if you disable ‘Create rules for safe applications’. It happens when that setting is applied, during shutdown, only when there are a mssive amount of rules existing.
CISfan has suggested several fixes that would take care of this, without Comodo having to re-do a bunch of code:
Blocked files makes sure nothing is allowed access to the file regardless of rating and there is no exceptions that can be done to allow access other than removing the file from blocked files. If you want to block a folder the path needs to end without the trailing backslash e.g. folder*, if you use folder\* then yes the folder is accessible but everything within it is not.
Yes, but in my testing it seems that this feature is not working properly. I will test more and respond back if anything changes. Thank you for the information regarding 'folder' , but the GUI should definitely be tweaked in this regard to make it more user-friendly.
Only way rules are auto created is only done through training mode or create rules for trusted applications setting, also verbose mode only applies to HIPS alerts.
What I am asking for, is that if verbose mode (HIPS) or high alert mode (FW) are enabled, then the ‘Training mode’ creates more fine tuned rules, according to these settings.
That is exactly what verbose mode alerts does, it specifies each unique action when enabled, or just one alert for each access right when disabled.
The issue though, is that say for example ‘High Alert’ mode is enabled, and the prompt specifies a specific IP / Port combination. There is no way to (via the prompt) edit the rule to only allow the port, but allow all IP. With HIPS ‘Verbose’ mode enabled, the issue is that, for example, the prompt is for a specific Protected Registry Key, but there is no way to (via the prompt) edit the rule to allow access for all Protected Registry Keys. I understand these modes allow for more fine-tuned rule creation (which I prefer), but they do not allow for the user to adjust the rules as they see fit (via the prompt). Some applications need access to a wide range of IP addresses, and some require access to a large amount of Protected registry keys, etc. The user must disable the FW or HIPS accordingly, reply to the prompt, go into Settings and manually adjust the rules, then re-enable the FW / HIPS. If the user leaves the FW / HIPS on while trying to manually fine tune the rules in the Settings, then they are bamboozled by the Prompt(s), because when they click Allow on the prompt, it applies ALL the settings of either the FW or HIPS that were existing at the time of the prompt first popping up. Instead of asking Comodo to re-code a bunch of things regarding how prompts interact with the settings database, the most simple (and elegant) solution would be to allow the user to do more custom fine-tuning via the prompt itself. This would also prevent the user from being forced to constantly disable FW / HIPS while setting up new computers. A lot of the things I am suggesting might seem to some people like they are a bit needy, but I truly believe the very large majority of my requests are absolutely required for a non-miserable experience while fine-tuning CIS. CIS is EXTRMELEY well designed and EXTREMELY powerful, but the GUI has areas where slight tweaks would be absolute GAME CHANGERS.