BUG in firewall rules some APS creating muptiple rules for each version repeating rules for each successive version

[tommy456 11]

ESET CREATES FIREWALL RULES REPEATEDLY WHEN IT SHOULDN'T NEED TO ON EVERY UPDATE  OPERA  AND ITS UPDATER APP, AND  A FEW OTHER PROGRAMS  cause this  nonsense within eset's firewall rules another is  over wolf that spring to mind  but there are many more  that are replicated  why no purging of obsolete rules

Edited December 13, 2021 by tommy456

[Marcos 4,694]

Are you positive that the path to the executables doesn't change as the applications update? Please provide logs collected with ESET Log Collector for a review of your firewall rules.

[SlashRose 25]

For some time now, Eset has been doing this with some updates, even if the path hasn't changed!

[tommy456 11]

I must have spent over a  hr deleting  the old entries , and the only changes are the updated builds

[Marcos 4,694]

Please provide logs collected by ESET Log Collector if you suspect duplicate fw rules to be created in interactive mode.

[itman 1,538]

I wonder if this has something to do with Eset's Application Modification Detection feature: https://help.eset.com/eis/15/en-US/idh_config_epfw_app_content_checking.html . This feature is active when the Firewall is in Interactive mode.

Possibly when this option is at default value:

Quote

Allow modification of signed (trusted) applications – Do not notify if the application has the same valid digital signature before and after the modification.

You won't get a notification and new rules are auto created regardless of if identical rules exist. If the option is disabled, you will get a notification about existing "permissive" rules with an option to keep them.

Edited December 14, 2021 by itman