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
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
NoVirusThanks OSArmor
Message
<blockquote data-quote="NoVirusThanks" data-source="post: 908808" data-attributes="member: 68429"><p>[USER=82776]@Lenny_Fox[/USER]</p><p></p><p></p><p></p><p>We will add better support for handling MSI executions:</p><p></p><p>We're working on adding support to use variables like %MSISIGNER% to match signer of a MSI file and %MSIPATH% to match MSI file path, so users can write custom block rules and exclusion rules by matching these new MSI-specific variables (e.g: you can block any MSI file, except the ones signed by a defined list of signers of your choice or you can allow MSI executions only in specific folder and signed by only specific vendors). We plan on adding also option to block execution of unsigned MSI files in Configurator -> Advanced tab. If you have other requirements or ideas please let me know.</p><p></p><p>[USER=72712]@Moonhorse[/USER]</p><p></p><p>I have asked FastSpring that but unfortunately they do not support it.</p><p></p><p>I'll ask if they plan on adding support for it soon and in case I will update you.</p></blockquote><p></p>
[QUOTE="NoVirusThanks, post: 908808, member: 68429"] [USER=82776]@Lenny_Fox[/USER] We will add better support for handling MSI executions: We're working on adding support to use variables like %MSISIGNER% to match signer of a MSI file and %MSIPATH% to match MSI file path, so users can write custom block rules and exclusion rules by matching these new MSI-specific variables (e.g: you can block any MSI file, except the ones signed by a defined list of signers of your choice or you can allow MSI executions only in specific folder and signed by only specific vendors). We plan on adding also option to block execution of unsigned MSI files in Configurator -> Advanced tab. If you have other requirements or ideas please let me know. [USER=72712]@Moonhorse[/USER] I have asked FastSpring that but unfortunately they do not support it. I'll ask if they plan on adding support for it soon and in case I will update you. [/QUOTE]
Insert quotes…
Verification
Post reply
Top