Possible Defense+ bug

I’m having a problem and i don’t know if it is a bug, so i wanted to get some help from the devs. I have a program (Asus Protect Manager) that creates interprocess memory hooks in all applications on access and for some reason firefox doesn’t like it, so i want to block the asus program from accessing the firefox’s memory thus i blocked the request. However for the rest of the apps and to avoid endless popups for every new application i use i added “File Groups → Executables” rule like in the screen shots belows.
My question is: shouldn’t the Blocked tab take priority over the Allowed one? If i don’t have the “File Groups → Executables” in the allowed tab it works fine, as in, it blocks the requests made by the asus process to Firefox.

Thanks (:KWL)





No one? :cry:

May be try the other way around. Edit the Firefox D+ rule to block the interprocess memory from the ASUS tool?

But that doesn’t answer my question “shouldn’t the Blocked tab take priority over the Allowed one?

No dev around to clarify this? (:WIN)

I believe the allowed tab always takes priority over the blocked. I have this in my own notes and I must have read it somewhere.

But shouldn’t it be the other way around?

This way we can allow “all” except “…”

By design Allowed list is prior to Blocked.
That’s make you able to block all but several exclusions, and if you want tot allow all but several exclusions tou can just add blocked applications w/o any in allowed list.
General priority is following:
first allowed list is consulted
then blocked list is consulted
if application was not found in both lists Defense+ takes [b]default action/b determined with three radio-buttons in access rights editor.

Thanks for the replies! (:HUG)

Now i understand how it works. Still it would be nice to have an option to change that behaviour so that blocked list took over priority first. For my problem, that would avoid having several entries in the registry for the allowed apps just to be able to block 1-2 i don’t want. This is a bigger problem because of the huge slowdown when the database (in registry) gets larger taking 5-10 seconds to “remember” an option. (:SAD)