Reply to thread

Message

<blockquote data-quote="Decopi" data-source="post: 1101323" data-attributes="member: 67091">The literature is abundant, it is very common to see a virus/malware hijacking the official SVCHOST signed by Microsoft. The same goes for other Windows Services.In the case of Comodo, there is an accumulation of serious technical failures:1. Comodo does not detect or identify virus/malware. Comodo is just a blocker, so Comodo puts the user at risk by forcing him to execute the virus/malware;2. Once the virus/malware is being executed, it can easily hijack other executables, for example the official SVCHOST signed by Microsoft. I repeat, signed or not signed, at Comodo any &quot;Safe&quot;/&quot;Trusted&quot; file has free comms;3. By default, Comodo labels as &quot;Safe&quot;/&quot;Trusted&quot; all the Windows Services, the Svchost, and hundreds of other files. It doesn&#039;t need to be signed! If the user or Comodo labeled a file as &quot;Safe&quot;/&quot;Trusted&quot;, that&#039;s it, end of history, that file will have free comms. All &quot;Safe&quot;/&quot;Trusted&quot; files have free comms at Comodo. It&#039;s worth remembering that in the past, Comodo labeled executables (that were viruses/malware) as &quot;Safe&quot;/&quot;Trusted&quot;. Those executables were not containerized/sandboxed, and Comodo Firewall gave them free comms. Again, this has happened in the past!;4. Considering that Comodo does not allow the customization of firewall rules for these &quot;Safe&quot;/&quot;Trusted&quot; files, every virus/malware can hijack these files, and obtain comms;5. Comodo is built in modules. The failure of a module (Firewall) cannot be justified by alleging that another module (Containment) avoids virus/malware comms. If Containment fails (and in the past it already failed many times), a virus/malware can hijack all the files considered &quot;Safe&quot;/&quot;Trusted&quot;, and Comodo not only does not detect or remove that virus/malware, as worse, Comodo Firewall allows free comms for that virus/malware.Comododo Firewall is a placebo.</blockquote>

[QUOTE="Decopi, post: 1101323, member: 67091"] The literature is abundant, it is very common to see a virus/malware hijacking the official SVCHOST signed by Microsoft. The same goes for other Windows Services. In the case of Comodo, there is an accumulation of serious technical failures: 1. Comodo does not detect or identify virus/malware. Comodo is just a blocker, so Comodo puts the user at risk by forcing him to execute the virus/malware; 2. Once the virus/malware is being executed, it can easily hijack other executables, for example the official SVCHOST signed by Microsoft. I repeat, signed or not signed, at Comodo any "Safe"/"Trusted" file has free comms; 3. By default, Comodo labels as "Safe"/"Trusted" all the Windows Services, the Svchost, and hundreds of other files. It doesn't need to be signed! If the user or Comodo labeled a file as "Safe"/"Trusted", that's it, end of history, that file will have free comms. All "Safe"/"Trusted" files have free comms at Comodo. It's worth remembering that in the past, Comodo labeled executables (that were viruses/malware) as "Safe"/"Trusted". Those executables were not containerized/sandboxed, and Comodo Firewall gave them free comms. Again, this has happened in the past!; 4. Considering that Comodo does not allow the customization of firewall rules for these "Safe"/"Trusted" files, every virus/malware can hijack these files, and obtain comms; 5. Comodo is built in modules. The failure of a module (Firewall) cannot be justified by alleging that another module (Containment) avoids virus/malware comms. If Containment fails (and in the past it already failed many times), a virus/malware can hijack all the files considered "Safe"/"Trusted", and Comodo not only does not detect or remove that virus/malware, as worse, Comodo Firewall allows free comms for that virus/malware. Comododo Firewall is a placebo. [/QUOTE]

Verification