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
Security
Video Reviews - Security and Privacy
Comodo Firewall 10 Setup
Message
<blockquote data-quote="AtlBo" data-source="post: 592623" data-attributes="member: 32547"><p>Have you had a problem with 360 TS web application? It creates a script when the browser opens. Comodo converts the script into a file and places it in a folder called Tempscrpt in the Programs area. If you haven't had a problem with it, it's the same problem, so not sure why unless you don't use it. It's really good though.</p><p></p><p>Here is what I have done for the 360 TS extension. Find the Tempscrpt folder in the Comodo folder in Programs. If you can set your explorer so you can view files this will help you see without opening the files. Otherwise, right click on each script and select "Edit" and make note of what application is creating/using each script (sounds like you may have done this). You will see it plainly in the script someplace.</p><p></p><p>Now go to Auto-Sandbox and create one for that application and set it to ignore. The Sticky Passwords uses Conhost.exe, so you may need to set an ignore rule for it too. Do this for each process you find in any script in the folder. If there's a rule there already in Auto-Sandbox rules for one, change it to ignore, assuming you trust the app.</p><p></p><p>If the WDPay (Safe Shopping) is not working for 360 (it won't work on my PC that has CFW without this), create an ignore rule for this too if you want the 360 browser extension to work.</p><p></p><p>If you have other rules, like firewall, you may want to go and set those rules so that each sandbox ignored application is treated as an "Allowed Application". Voodoo Shield is surely giving you a VS alert every time the browser opens too (unless you used a wildcard edit for the Sticky PW command line). Is this correct? Anyway, you will still get a Comodo pop up when the browser opens for extensions that make a script no matter what. If you deal with the pop up correctly the first time, the rule will stay "ignore" and the extension will run outside the sandbox and normally. The first time I got this, I chose to allow the script as and Treat it as "Allowed Application" or selected "ignore" can't remember the alert. After this the alert will come every time still, but the application is not sandboxed as long as the same choice is made. It will still be ignored. The 360 extension works as it's supposed to work now for me.</p><p></p><p>If you are only having the issue with the Sticky Password extension, the above should work...I think anyway.</p><p></p><p></p><p></p><p>If this somehow had anything to do with this, I don't know. Maybe it works anyway even if HIPs is enabled? I won't turn this off, though...no way. This monitors all scripts at least for the HIPs module, and it's very powerful. I have HIPs enabled, so I can't say if it will still work anyway as the setting that causes script monitoring. Maybe script monitoring happens separately from HIPs and automatically for sandboxing without a setting in that area.</p><p></p><p>BTW, you can see in the Tempscrpt folder that these will build up over time. I guess I will come up with a cleaning solution for this that works by date/time/exclusions, etc. Some of the scripts must be in the folder for PCs here, so they can't be deleted without getting a pop up later.</p><p></p><p>Apologies so long, hope it helps somehow. Hope Comodo come up with something for this soon. I know they know about it already.</p></blockquote><p></p>
[QUOTE="AtlBo, post: 592623, member: 32547"] Have you had a problem with 360 TS web application? It creates a script when the browser opens. Comodo converts the script into a file and places it in a folder called Tempscrpt in the Programs area. If you haven't had a problem with it, it's the same problem, so not sure why unless you don't use it. It's really good though. Here is what I have done for the 360 TS extension. Find the Tempscrpt folder in the Comodo folder in Programs. If you can set your explorer so you can view files this will help you see without opening the files. Otherwise, right click on each script and select "Edit" and make note of what application is creating/using each script (sounds like you may have done this). You will see it plainly in the script someplace. Now go to Auto-Sandbox and create one for that application and set it to ignore. The Sticky Passwords uses Conhost.exe, so you may need to set an ignore rule for it too. Do this for each process you find in any script in the folder. If there's a rule there already in Auto-Sandbox rules for one, change it to ignore, assuming you trust the app. If the WDPay (Safe Shopping) is not working for 360 (it won't work on my PC that has CFW without this), create an ignore rule for this too if you want the 360 browser extension to work. If you have other rules, like firewall, you may want to go and set those rules so that each sandbox ignored application is treated as an "Allowed Application". Voodoo Shield is surely giving you a VS alert every time the browser opens too (unless you used a wildcard edit for the Sticky PW command line). Is this correct? Anyway, you will still get a Comodo pop up when the browser opens for extensions that make a script no matter what. If you deal with the pop up correctly the first time, the rule will stay "ignore" and the extension will run outside the sandbox and normally. The first time I got this, I chose to allow the script as and Treat it as "Allowed Application" or selected "ignore" can't remember the alert. After this the alert will come every time still, but the application is not sandboxed as long as the same choice is made. It will still be ignored. The 360 extension works as it's supposed to work now for me. If you are only having the issue with the Sticky Password extension, the above should work...I think anyway. If this somehow had anything to do with this, I don't know. Maybe it works anyway even if HIPs is enabled? I won't turn this off, though...no way. This monitors all scripts at least for the HIPs module, and it's very powerful. I have HIPs enabled, so I can't say if it will still work anyway as the setting that causes script monitoring. Maybe script monitoring happens separately from HIPs and automatically for sandboxing without a setting in that area. BTW, you can see in the Tempscrpt folder that these will build up over time. I guess I will come up with a cleaning solution for this that works by date/time/exclusions, etc. Some of the scripts must be in the folder for PCs here, so they can't be deleted without getting a pop up later. Apologies so long, hope it helps somehow. Hope Comodo come up with something for this soon. I know they know about it already. [/QUOTE]
Insert quotes…
Verification
Post reply
Top