Author Topic: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4  (Read 12417 times)

0 Members and 1 Guest are viewing this topic.

MaxReed

  • Guest
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #15 on: July 09, 2011, 12:08:58 PM »
But with these changes,however, is my PC protected good?  :-\

Offline SpeedyPC

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 3398
  • Avast shall conquer the whole world
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #16 on: July 09, 2011, 02:15:35 PM »
But with these changes,however, is my PC protected good?  :-\

Yes your PC is protected ;) keep in mind you don't need two sandbox running at the same time Comodo and Avast, the only sandbox you need is Avast not Comodo cause this is over killed.

Your Comodo Defense+ is still enable this is how it works without using Comodo Sandbox.

The Defense+ component of Comodo Internet Security (hereafter known simply as Defense+) is a host intrusion prevention system that constantly monitors the activities of all executable files on your PC. With Defense+ activated, the user is warned EVERY time an unknown application executable (.exe, .dll, .sys, .bat etc) attempts to run. The only executables that are allowed to run are the ones you give permission to.

Defense+ also protects against data theft, computer crashes and system damage by preventing most types of buffer overflow attacks. This type of attack occurs when a malicious program or script deliberately sends more data to its memory buffer than that the buffer can handle. It is at this point that a successful attack can create a back door to the system through which a hacker can gain access. The goal of most attacks is to install malware onto the compromised PC whereby the hacker can reformat the hard drive, steal sensitive user information, or even install programs that transform the machine into a Zombie PC.

Defense+ boasts a highly configurable security rules interface and prevents possible attacks from root-kits, inter-process memory injections, key-loggers and more. It blocks Viruses, Trojans and Spyware before they can ever get installed on your system and prevents unauthorized modification of critical operating system files and registry entries.


I forgot to tell sorry set your Firewall Security Level to Custom Policy and set your Defense+ Security Level to Paranoid Mode and finally look for Stealth Ports Wizard and pick Block all incoming connections that all ;)
« Last Edit: July 10, 2011, 07:56:13 AM by SpeedyPC »
Gigabyte 670 LGA1200 Full ATX MB | Intel Core i9-13900 CPU/LGA 1700 | GeForce Nvidia RTX-4070/12GB | 32GB DDR4 | 2 x 1TB Samsung SSD | W11 Home 64bit | Avast Premium v24.3.6108 | Avast SecureLine VPN | Avast Secure Browser | Avast Driver Updater | Avast BreachGuard | Firefox 64bit | MalwareBytes Premium | Adguard Premium | CCleaner Portable | Macrium Reflect | 7-Zip

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89029
  • No support PMs thanks
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #17 on: July 09, 2011, 03:23:00 PM »
Well this is becoming more prevalent by a number of security applications as it speeds up any scan/check as accessing this data is much quicker if the signature data is loaded in memory rather than on the hard drive.

So the rights and wrongs of it those signatures when loaded in memory should be encrypted or not, as they must know there is a possibility that the users resident anti-virus may well detect these signatures. Or is it just the case that, since comodo now only offer the suite version with an AV and feel there shouldn't be anyone who doesn't want their AV (or care).

If the signatures were encrypted in memory they wouldn't/shouldn't be detected, but then there is the overhead of having to decrypt the signatures first, losing some of the benefit of having them in memory.

So in essence it is up to the user, to do as I suggested don't run the memory scan in the custom scan or ignore the expected results if virus signatures loaded by security software are detected.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 76037
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #18 on: July 09, 2011, 06:25:12 PM »
A bit OT, but if you just need a quite slick FW (and eventually a HIPS) use an older version of Comodo. (See my sig.!) This version doesn't load any signatures into memory and does everything you can expect from a FW (and a HIPS). ;)
W8.1 [x64] - Avast Free AV 23.3.8047.BC [UI.757] - Firefox ESR 102.9 [NS/uBO/PB] - Thunderbird 102.9.1
Avast-Tools: Secure Browser 109.0 - Cleanup 23.1 - SecureLine 5.18 - DriverUpdater 23.1 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline Para-Noid

  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 6700
  • Trust only what you test yourself!
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #19 on: July 09, 2011, 06:33:40 PM »
A bit OT, but if you just need a quite slick FW (and eventually a HIPS) use an older version of Comodo. (See my sig.!) This version doesn't load any signatures into memory and does everything you can expect from a FW (and a HIPS). ;)
I noticed you mentioned HIPS, I have been using Online Armor Free which has HIPS and does not slow down my machine. I was wondering if Comodo does like wise? I am asking for my knowledge because I have never used anything from Comodo. I am constantly trying to learn.  :)

I found this link so anyone could download an earlier version.
http://filehippo.com/download_comodo/
Dell Inspiron, Win10x64--HP Envy Win10x64--Both systems Avast Free v17.9.2322, Comodo Firewall v8.2 w/D+, MalwareBytes v3.0, OpenDNS, Super Anti-Spyware, Spyware Blaster, MCShield, Unchecky, Vivaldi Browser and, various browser security tools.

"Look before you leap!" Use online scanners before you click on any link.

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 76037
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #20 on: July 09, 2011, 06:38:18 PM »
I noticed you mentioned HIPS, I have been using Online Armor Free which has HIPS and does not slow down my machine. I was wondering if Comodo does like wise?

You mean, if Comodo's HIPS (D+) slows your system..?
No, it doesn't.
W8.1 [x64] - Avast Free AV 23.3.8047.BC [UI.757] - Firefox ESR 102.9 [NS/uBO/PB] - Thunderbird 102.9.1
Avast-Tools: Secure Browser 109.0 - Cleanup 23.1 - SecureLine 5.18 - DriverUpdater 23.1 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline Para-Noid

  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 6700
  • Trust only what you test yourself!
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #21 on: July 09, 2011, 07:41:54 PM »


You mean, if Comodo's HIPS (D+) slows your system..?
No, it doesn't.
[/quote]
That's what I wanted to know. Thanks.  :)
Dell Inspiron, Win10x64--HP Envy Win10x64--Both systems Avast Free v17.9.2322, Comodo Firewall v8.2 w/D+, MalwareBytes v3.0, OpenDNS, Super Anti-Spyware, Spyware Blaster, MCShield, Unchecky, Vivaldi Browser and, various browser security tools.

"Look before you leap!" Use online scanners before you click on any link.

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 76037
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #22 on: July 09, 2011, 08:33:49 PM »
That's what I wanted to know. Thanks.  :)

You're welcome..!
W8.1 [x64] - Avast Free AV 23.3.8047.BC [UI.757] - Firefox ESR 102.9 [NS/uBO/PB] - Thunderbird 102.9.1
Avast-Tools: Secure Browser 109.0 - Cleanup 23.1 - SecureLine 5.18 - DriverUpdater 23.1 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

DBone

  • Guest
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #23 on: July 10, 2011, 01:03:10 AM »
I know an easy fix...............Uninstall Comodo, and use Windows FW.

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 76037
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #24 on: July 10, 2011, 01:07:35 AM »
I know an easy fix...............Uninstall Comodo, and use Windows FW.

Whom do you address..?
W8.1 [x64] - Avast Free AV 23.3.8047.BC [UI.757] - Firefox ESR 102.9 [NS/uBO/PB] - Thunderbird 102.9.1
Avast-Tools: Secure Browser 109.0 - Cleanup 23.1 - SecureLine 5.18 - DriverUpdater 23.1 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

DBone

  • Guest
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #25 on: July 10, 2011, 01:45:16 AM »
Nobody specific, just what I would do. :)

DonZ63

  • Guest
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #26 on: July 10, 2011, 02:04:00 AM »
SpeedyPC, have any suggestions for MBAM Pro that is loading 6-7 unencrypted signatures into memory? At least that is what Avast's memory scanner is saying.

It is a bit odd that Avast's memory scanner is not only flaging Comodo's cmdagent.exe but also MBAM's mbamservice.exe.

I am also curious as to why you are recommending that all Defense+ cloud settings be turned off. Know something amiss in that area?

BTW - cmdagent.exe is loading snxhk64.dll which is an Avast .dll. I was floored when I saw that. More so since Comodo really protects the hell out of cmdagent.exe.
« Last Edit: July 10, 2011, 02:09:25 AM by DonZ63 »

Offline SpeedyPC

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 3398
  • Avast shall conquer the whole world
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #27 on: July 10, 2011, 07:07:29 AM »
A bit OT, but if you just need a quite slick FW (and eventually a HIPS) use an older version of Comodo. (See my sig.!) This version doesn't load any signatures into memory and does everything you can expect from a FW (and a HIPS). ;)

The old Comodo FW v3.14 doesn't work on Win7 just keep this in mind ;)
Gigabyte 670 LGA1200 Full ATX MB | Intel Core i9-13900 CPU/LGA 1700 | GeForce Nvidia RTX-4070/12GB | 32GB DDR4 | 2 x 1TB Samsung SSD | W11 Home 64bit | Avast Premium v24.3.6108 | Avast SecureLine VPN | Avast Secure Browser | Avast Driver Updater | Avast BreachGuard | Firefox 64bit | MalwareBytes Premium | Adguard Premium | CCleaner Portable | Macrium Reflect | 7-Zip

Offline SpeedyPC

  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 3398
  • Avast shall conquer the whole world
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #28 on: July 10, 2011, 07:28:11 AM »
@DonZ63 I cannot answer your question about MBAM Pro I only used the free version, I'm also aware that has extra features in the Pro version so I cannot fully answer your question along side with Comodo FW.

The Comodo FW cloud feature is a bit over kill when Avast free has so many extra feature that protecting your PC, Comodo cloud can cause to many FP if your not very careful with it. I also have other software for On-demand on my PC and I also have CCE ;) All I'm saying is with all the extra security feature in Comodo FW is over killed while Avast free is almost doing the same the job, so why add more when you over killed the PC can create a lot problems. The only way to balance this problem out you either remove Avast to have all the CIS feature, and if you want to used Avast than cut down the feature running inside Comodo FW you can't have both ways.
« Last Edit: July 10, 2011, 08:05:13 AM by SpeedyPC »
Gigabyte 670 LGA1200 Full ATX MB | Intel Core i9-13900 CPU/LGA 1700 | GeForce Nvidia RTX-4070/12GB | 32GB DDR4 | 2 x 1TB Samsung SSD | W11 Home 64bit | Avast Premium v24.3.6108 | Avast SecureLine VPN | Avast Secure Browser | Avast Driver Updater | Avast BreachGuard | Firefox 64bit | MalwareBytes Premium | Adguard Premium | CCleaner Portable | Macrium Reflect | 7-Zip

Offline CraigB

  • Avast Überevangelist
  • Serious Graphoman
  • *****
  • Posts: 11239
  • No support PM's thanks
Re: Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4
« Reply #29 on: July 10, 2011, 08:00:16 AM »
DonZ63 if you are getting memory detections about malwarebytes then you must be running a custom scan with memory scan included, as this scan tends to delve deeper into memory than the normal scans which is why your picking up MBAM signitures, there is no way round it but to either untick the memory scan section or to stick to the normal scans, or simply just ignore the detections of MBAM as there harmless anyway.