Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Other security for Windows, Mac, Linux
EXE Radar Pro v4 (Beta)
Message
<blockquote data-quote="Snickers102" data-source="post: 751099" data-attributes="member: 73418"><p>Test 21 works great! Everything's good now</p><p></p><p>I think "Add as rule" or simply "Remember action" (or just "Remember") is better than "Remember this action." , the dot also makes it look worse</p><p></p><p>As far as I tested, the priority order is Exclude > Deny > Ask > Allow, so Allow has the lowest priority</p><p></p><p>Would be useful if the user can create priorities. Let's say a priority has 3 types, either allow, deny or ask, and each priority will have a number. The number, for example between 1 and 9, will indicate how strong the priority is. For example, Allow[3] is stronger than Deny[2], so if cmd.exe from system32 has priority Deny[2] but a specific batch file has priority Allow[3], the batch file gets allowed to run since the rule takes priority over the deny cmd.exe rule since 3 is a higher number than 2. But then let's say that same batch file with additional properties (such as when started by a specific parent process) has priority of Deny[4], then that specific batch file will get denied when started by the specified parent process from the Deny[4] rule. And then let's say we have Ask[5] rule of that specific batch file, when started by that same parent process, but the parent process has a different (or no) signer. Then, we'd get asked whether to allow that specific batch file started by that specific parent process, since this Ask[5] rule takes priority over the Deny[4] rule (which specifies a specific parent process and a specific signer, while Ask[5] doesn't have that specific signer), which takes priority over Allow[3] which has no specific parent process in the rule, which takes priority over Deny[2] which denies any batch file (started from cmd.exe child process) without a higher priority rule. I think only 2 levels of priority for allow (level 1 being exclude and level 2 being allow), and only 1 level for deny and 1 level for ask is too little, in the above scenario these 4 rule priorities with only a total combined of 4 levels would not be anywhere near enough for what someone might be trying to do with a case like that</p><p></p><p>It would also be pretty cool if there was a manual, cuz I have 0 idea how I'm supposed to use wildcards, they don't work like excubits' wildcards (for example), I simply don't know the syntax of Exe Radar Pro, just plain "*" instead of a character doesn't seem to work</p><p></p><p>And, to top it off for now, how about we can customize the color of the tray icon shield? For example, I may want my alert mode icon to be in blue or green, not red, cuz red doesn't "merge" well with the color of my other tray icons, it makes it looks ugly when there's so much potential to look cool, if only at least 1 developer was like "let's let users choose their own color" instead of forcing us to use whatever color they picked and ruining our taskbar icon color sync</p><p></p><p>EDIT: Forgot to mention, a VERY important feature still missing, files that no longer exist and have a specified path should get automatically deleted from the rules list, this makes the rule list a lot bigger than it should be over time and every few weeks I have to reset it cuz it just gets so huge after accumulating so many useless leftover rules</p></blockquote><p></p>
[QUOTE="Snickers102, post: 751099, member: 73418"] Test 21 works great! Everything's good now I think "Add as rule" or simply "Remember action" (or just "Remember") is better than "Remember this action." , the dot also makes it look worse As far as I tested, the priority order is Exclude > Deny > Ask > Allow, so Allow has the lowest priority Would be useful if the user can create priorities. Let's say a priority has 3 types, either allow, deny or ask, and each priority will have a number. The number, for example between 1 and 9, will indicate how strong the priority is. For example, Allow[3] is stronger than Deny[2], so if cmd.exe from system32 has priority Deny[2] but a specific batch file has priority Allow[3], the batch file gets allowed to run since the rule takes priority over the deny cmd.exe rule since 3 is a higher number than 2. But then let's say that same batch file with additional properties (such as when started by a specific parent process) has priority of Deny[4], then that specific batch file will get denied when started by the specified parent process from the Deny[4] rule. And then let's say we have Ask[5] rule of that specific batch file, when started by that same parent process, but the parent process has a different (or no) signer. Then, we'd get asked whether to allow that specific batch file started by that specific parent process, since this Ask[5] rule takes priority over the Deny[4] rule (which specifies a specific parent process and a specific signer, while Ask[5] doesn't have that specific signer), which takes priority over Allow[3] which has no specific parent process in the rule, which takes priority over Deny[2] which denies any batch file (started from cmd.exe child process) without a higher priority rule. I think only 2 levels of priority for allow (level 1 being exclude and level 2 being allow), and only 1 level for deny and 1 level for ask is too little, in the above scenario these 4 rule priorities with only a total combined of 4 levels would not be anywhere near enough for what someone might be trying to do with a case like that It would also be pretty cool if there was a manual, cuz I have 0 idea how I'm supposed to use wildcards, they don't work like excubits' wildcards (for example), I simply don't know the syntax of Exe Radar Pro, just plain "*" instead of a character doesn't seem to work And, to top it off for now, how about we can customize the color of the tray icon shield? For example, I may want my alert mode icon to be in blue or green, not red, cuz red doesn't "merge" well with the color of my other tray icons, it makes it looks ugly when there's so much potential to look cool, if only at least 1 developer was like "let's let users choose their own color" instead of forcing us to use whatever color they picked and ruining our taskbar icon color sync EDIT: Forgot to mention, a VERY important feature still missing, files that no longer exist and have a specified path should get automatically deleted from the rules list, this makes the rule list a lot bigger than it should be over time and every few weeks I have to reset it cuz it just gets so huge after accumulating so many useless leftover rules [/QUOTE]
Insert quotes…
Verification
Post reply
Top