Reply to thread

Message

<blockquote data-quote="plat" data-source="post: 894602" data-attributes="member: 74969">What I&#039;m wondering is if CFA is too slow to block for certain programs.&nbsp; Here&#039;s an example from personal experience:&nbsp; Some time ago, OSArmor couldn&#039;t block legacy Edge from opening if Edge was enabled to run in the background.&nbsp; It would throw an alert as if a block happened but legacy Edge would open unhindered and function perfectly.So another point I&#039;m making:&nbsp; just because you get an alert, it apparently doesn&#039;t mean squat in some cases.&nbsp; Which leads back to my original dilemma;&nbsp; is it worth keeping enabled?&nbsp; I&#039;ll need more info and will try to get that elsewhere.If I&#039;m aware of contingencies like this, I can make better decisions about what to keep or discard on my machine.&nbsp; In OSA&#039;s case it was a matter of toggling certain background apps running in the bkgrd to OFF and it&#039;s a keeper, then.&nbsp; Here, I&#039;m not so sure.</blockquote>

[QUOTE="plat, post: 894602, member: 74969"] What I'm wondering is if CFA is too slow to block for certain programs. Here's an example from personal experience: Some time ago, OSArmor couldn't block legacy Edge from opening if Edge was enabled to run in the background. It would throw an alert as if a block happened but legacy Edge would open unhindered and function perfectly. So another point I'm making: just because you get an alert, it apparently doesn't mean squat in some cases. Which leads back to my original dilemma; is it worth keeping enabled? I'll need more info and will try to get that elsewhere. If I'm aware of contingencies like this, I can make better decisions about what to keep or discard on my machine. In OSA's case it was a matter of toggling certain background apps running in the bkgrd to OFF and it's a keeper, then. Here, I'm not so sure. [/QUOTE]

Verification