Reply to thread

Message

<blockquote data-quote="NoVirusThanks" data-source="post: 1021209" data-attributes="member: 68429">[USER=91306]@wat0114[/USER]Here is a screenshot (mainly added these two fields to be matched in Exclusions Helper GUI):[ATTACH=full]272340[/ATTACH][USER=97580]@Andrezj[/USER]OSArmor by default blocks the process behavior and shows the alert to the user after it has been already blocked.If we add an &quot;Allow Once&quot; option it would allow the event once but only on the next time the process behavior is detected.We may discuss about add an option like &quot;Exclude for N minutes&quot; probably, like a temporary exclusion that is not written to Exclusions.db file.The quick way to handle this scenario at the moment is to like disable protection when installing a safe and trusted application and re-enable protection once done (just an example).Or can be enabled the option &quot;Passive Logging&quot; so all process blocked events are only logged and not blocked.</blockquote>

[QUOTE="NoVirusThanks, post: 1021209, member: 68429"] [USER=91306]@wat0114[/USER] Here is a screenshot (mainly added these two fields to be matched in Exclusions Helper GUI): [ATTACH type="full"]272340[/ATTACH] [USER=97580]@Andrezj[/USER] OSArmor by default blocks the process behavior and shows the alert to the user after it has been already blocked. If we add an "Allow Once" option it would allow the event once but only on the next time the process behavior is detected. We may discuss about add an option like "Exclude for N minutes" probably, like a temporary exclusion that is not written to Exclusions.db file. The quick way to handle this scenario at the moment is to like disable protection when installing a safe and trusted application and re-enable protection once done (just an example). Or can be enabled the option "Passive Logging" so all process blocked events are only logged and not blocked. [/QUOTE]

Verification