Reply to thread

Message

<blockquote data-quote="Decopi" data-source="post: 1101398" data-attributes="member: 67091">At Comodo, IPv6 is an old unfixed bug since 2017, many and many times reported at official Comodo forum... another bug among around other 500 accumulated bugs.You can use Comodo or whatever you want. You are free to use and you have the right to use whatever you want.I&#039;m only saying that what&#039;s good for you might be bad, wrong and dangerous for 99,99% of the users.Deleting the safe list will not solve Comodo Firewall design flaw. That&#039;s because you&#039;re going to have files and apps requesting the use of Windows Services, or Svchost, or another files. And Comodo Firewall doesn&#039;t allow to customize these files. For example, At Comodo Firewall you can make general rules for svchost, but you can&#039;t make specify rules when svchost is used by X.exe or Y.exe. So in this example, at your new safe customized list you are going to label &quot;svchost&quot; as &quot;safe&quot;/&quot;trusted&quot;... and then you will have exactly the same problem that Comodo Firewall default settings have with the original safe list.There is no solution to the Comodo Firewall design flaw.Comodo Firewall is a placebo.PS: Windows Firewall and many other third-party firewall software allow the complete customization of almost any file.</blockquote>

[QUOTE="Decopi, post: 1101398, member: 67091"] At Comodo, IPv6 is an old unfixed bug since 2017, many and many times reported at official Comodo forum... another bug among around other 500 accumulated bugs. You can use Comodo or whatever you want. You are free to use and you have the right to use whatever you want. I'm only saying that what's good for you might be bad, wrong and dangerous for 99,99% of the users. Deleting the safe list will not solve Comodo Firewall design flaw. That's because you're going to have files and apps requesting the use of Windows Services, or Svchost, or another files. And Comodo Firewall doesn't allow to customize these files. For example, At Comodo Firewall you can make general rules for svchost, but you can't make specify rules when svchost is used by X.exe or Y.exe. So in this example, at your new safe customized list you are going to label "svchost" as "safe"/"trusted"... and then you will have exactly the same problem that Comodo Firewall default settings have with the original safe list. There is no solution to the Comodo Firewall design flaw. Comodo Firewall is a placebo. PS: Windows Firewall and many other third-party firewall software allow the complete customization of almost any file. [/QUOTE]

Verification