Reply to thread

Message

<blockquote data-quote="Decopi" data-source="post: 1100297" data-attributes="member: 67091">Please, allow me to paste the same comment I made to your other similar post:In general, I totally agree with your comment.But comms is just the tip of the iceberg. If the device is infected, firewall can do almost nothing to solve the problem. Here a real modern antivirus/malware is needed.Also, take the example of Comodo, an abandonware since 2017 + full of unfixed bugs... by default, Comodo Firewall allows comms for &quot;safe files&quot;, where &quot;safe files&quot; is just an arbitrary list made by Comodo (last update 15 years ago). Under this category you will find SYSTEM, Windows Services, SVCHOST etc etc etc... I repeat, all allowed by Comodo default. And in real life, it&#039;s possible to find thousand of cases where virus/malware hijacked all these &quot;safe files&quot; allowed by Comodo, and managed to have comms. And considering that Comodo can&#039;t customize fiirewall rules for Windows Services, Svchost etc, &quot;default deny&quot; doesn&#039;t work here.Again, I agree with you, I&#039;m just complementing by saying that &quot;default deny&quot; is not the panacea, not for files, nor for comms. And average users have zero chance to deal with &quot;default deny&quot; strategies.</blockquote>

[QUOTE="Decopi, post: 1100297, member: 67091"] Please, allow me to paste the same comment I made to your other similar post: In general, I totally agree with your comment. But comms is just the tip of the iceberg. If the device is infected, firewall can do almost nothing to solve the problem. Here a real modern antivirus/malware is needed. Also, take the example of Comodo, an abandonware since 2017 + full of unfixed bugs... by default, Comodo Firewall allows comms for "safe files", where "safe files" is just an arbitrary list made by Comodo (last update 15 years ago). Under this category you will find SYSTEM, Windows Services, SVCHOST etc etc etc... I repeat, all allowed by Comodo default. And in real life, it's possible to find thousand of cases where virus/malware hijacked all these "safe files" allowed by Comodo, and managed to have comms. And considering that Comodo can't customize fiirewall rules for Windows Services, Svchost etc, "default deny" doesn't work here. Again, I agree with you, I'm just complementing by saying that "default deny" is not the panacea, not for files, nor for comms. And average users have zero chance to deal with "default deny" strategies. [/QUOTE]

Verification