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
NVT ERP to block Chromium Edge
Message
<blockquote data-quote="Andy Ful" data-source="post: 814135" data-attributes="member: 32260"><p>The problem is with WD Application Guard extension which is loaded by Edge Dev via command line. This command line should be whitelisted. Though, after whitelisting, everything should work well for a few days, until the extension will change its version. For whitelisting it permanently, the wildcards have to be used, as it was mentioned by [USER=37647]@shmu26[/USER].</p><p></p><p>It is also possible that the below part of the command line is changing on each running of Edge Dev:</p><p><em>chrome.nativeMessaging.in.8599a1ee4c891f53 > \\.\pipe\chrome.nativeMessaging.out.8599a1ee4c891f53</em></p><p>If so, then this should be also replaced with wildcards, for example:</p><p><em>chrome.nativeMessaging.in.* > \\.\pipe\chrome.nativeMessaging.out.*</em></p><p><em></em></p><p><em>When using wildcards in Exe Radar Pro, one must remember to change the "Command Line" setting: 'Equal to" ----> "Like to (Wildcard)".</em></p></blockquote><p></p>
[QUOTE="Andy Ful, post: 814135, member: 32260"] The problem is with WD Application Guard extension which is loaded by Edge Dev via command line. This command line should be whitelisted. Though, after whitelisting, everything should work well for a few days, until the extension will change its version. For whitelisting it permanently, the wildcards have to be used, as it was mentioned by [USER=37647]@shmu26[/USER]. It is also possible that the below part of the command line is changing on each running of Edge Dev: [I]chrome.nativeMessaging.in.8599a1ee4c891f53 > \\.\pipe\chrome.nativeMessaging.out.8599a1ee4c891f53[/I] If so, then this should be also replaced with wildcards, for example: [I]chrome.nativeMessaging.in.* > \\.\pipe\chrome.nativeMessaging.out.* When using wildcards in Exe Radar Pro, one must remember to change the "Command Line" setting: 'Equal to" ----> "Like to (Wildcard)".[/I] [/QUOTE]
Insert quotes…
Verification
Post reply
Top