DEE
Newbie


Posts: 5
|
 |
If you use Outpost w/ Component Control Activated
« on: Sep 7th, 2006, 7:06pm » |
Quote Modify
|
Thanks to Jrb..This post is in case it comes up again on this forum... This is for users experiencing component control pop ups from Agnitums Outpost Firewall after installing TrojanHunter 4.6 From this thread: http://forum.misec.net/board/TrojanHunter;action=display;num=1157392159; start= Quote:Hi DEE, Forget for the moment NISFileCheck (yep, I know about that archived forum at Wilders; I've posted there Wink). posted by Jrb About Outpost: I don't know from own experience how it works and how it tells that a dll-file has been changed (that could be by checking a checksum, by checking a full-path, etc). Originally I understood that you had your problems coming up after installing TH 4.6. But now I understand that you had it also with version 4.5. I also understand that you have only recently installed Outpost. The best advice I can give: start a new thread here and ask users of both TH and Outpost how to let them work nicely together. I know there are users who are running them both!!! In the meanwhile I hope that that infection you were talking about, is not interfering here... Cheers, Jan. |
| ________________________________________________ From the help section of Outpost firewall: If a component of an application has been changed and the application is about to establish a connection, Outpost Firewall Pro will inform you of the changed component and ask whether this connection should be allowed. The technology responsible for that is called Component Control and its purpose is to make sure no fake and malicious components get network access. You can set up the desired Component Control level. Click Options on the toolbar, select the Application tab, and click the Components button. The following levels are available in the Component Control Settings window: *Normal - Outpost Firewall Pro will monitor all new components as they are being registered to be a part of an application yet are not located in the application folder and all updated components and remember the legitimate ones in its database. This option is suitable for most cases and provides a balance between security and performance. *Maximum - Outpost Firewall Pro will monitor all components that are being registered as part of a legitimate application. It is recommended that you use this option only when you suspect an unknown malware to exist in your system because this option may seriously impact on your system performance. *Disabled - turns Component Control off. This option is only recommended when you experience significantly reduced performance, crashes, or other errors that lead to system instability. Turning Component Control off severely reduces your system's security level as Outpost Firewall Pro no longer monitors each application component. Changing levels affects all applications and their components. It is not possible to change the level for specific applications. Note: It is not recommended to use the Maximum level unless you are sure your system is being threatened by a virus, Trojan or other malicious program. ____________________________________________________ I have my Outpost set to advanced settings, & component control set for maximum security. That's why the issue arose for me. These directions can be found on your Agnitum Outpost Firewalls help section under- Protecting from Malicious Process Activity/Controlling Application Components.
|
|
IP Logged |
|
|
|