Feature Requests For CIS

TWO HIPS FEATURE REQUESTS
An editable input field to define an Allowed Path in COMODO HIPS Pop-up Installing any random app, in the pop-up, please show the path requesting the permission in an editable field, so that user can edit the path and add an asterisk to allow free writing inside that path, but that path only. (That feature would have saved a ton of time if it was there from the begining of times, 2005 or so) Blocked Files expanded to per-application-basis Any random online-access-requiring installer / license manager creates a need for an ability in COMODO to setup a path or paths that are the only accessible paths for these applications. Everything else in the machine must be unREADable - as any file/directory in the Blocked Files listing currently is. To achieve this, please expand the current version of the Blocked Files functionality to as-per-application bases. It could well be, if you like, shown behind an 'EXTREME MODE' switch (or whatever name you prefer), but that way any app could be completely jailed slash controlled directly. An inverse mode check box, eg. "block everything except this" would be a good thing. This way Comodo HIPS could jail any app to its very own directories without an ability to write AND read outside it (as we know, a lot of apps attempt to read all-over the palace, one of such apps being Spotify's earlier versions). This addition would make even Windows 10 a very privacy safe platform. Comodo HIPS and Firewall already make Windows, even the nosey 10 and 11, very privacy secured when correctly configured. Thanks a lot for your great work! Very grateful for this one-of-a-kind application.
0
More convenient adjustment of alert frequency/rule creation
In version 12.2 the Comodo firewall allows to adjust the number of alert pop-ups using the option "Set alert frequency level": this ranges from 'Low' to 'Very High'. This directly influences the way rules are being created or extended when a specific alert is blocked or allowed. However, the level of detail can only be adjusted in a fixed sequence, which is: Outgoing/Incoming -> TCP/UDP -> Port-wise -> IP-adress-wise. Therefore, if I want rules to be created specific for the IP-address, I will get rules only for the specific port of that alert (and either for TCP or UDP and Outgoing/Incoming). However, I often do want rules specific for the IP-address but not specific for the port. Therefore, after a rule is created when I answered to an alert, I have to manually open the firewall options, find the specific rule and adjust its setting for source/target port. This is quite annoying. I can think of the following two enhancements that would improve this: (1) The setting "Set alert frequency level" is extended by an option "Individually". If "Individually" is chosen, then the different rule criteria can be activated separately (i.e. Outgoing/Incoming, TCP/UDP, Port, IP-adress). (2) Offering on each single alert the option to create the rule specific to these criteria (i.e. ignoring the option "Set alert frequency level" for this specific alert). This would allow that for a specific program the rule creation could be made more or less detailed. It would probably be a good idea to have a setting that would activate/deactivate this option. I think both suggestions would be an improvement on their own, but having both would be even better.
1
Load More