Yeah, that's why I reluctantly had to quit Comodo products... even when Windows 10 Anniversary Update came out, they took one month to release a product that was compatible with it (drivers signed by Microsoft). On their forum I read a lot of complaints from users that test Windows Insider Builds. Then, the fiasco with Microsoft Update KB4022716...
Hi all https://forums.comodo.com/beta-corn...t-security-v10016286-hotfix-rc-t120393.0.html Comodo Internet Security v.10.0.1.6286 Hotfix RC With best Regards Mops21
Hi all Comodo Internet Security v.10.0.1.6292 Hotfix RC 2 https://forums.comodo.com/beta-corn...-security-v10016292-hotfix-rc2-t120441.0.html With best Regards Mops21
Hi all https://forums.comodo.com/news-anno...rity-v10016294-hotfix-released-t120447.0.html Comodo Internet Security v.10.0.1.6294 (Hotfix) With best Regards Mops21
latest release of CIS10 and edge works in the latest insider again... obviously they DO test against insider, patience is a virtue, so hold yer horses before condemning it.
Yes, since umesh has taken the lead, Comodo products are getting better and better I've updated my CFW and I've really been impressed for how smooth the process has gone
forgot to say, this last MS Insider update this weekend i, for devilment, left CIS enabled and it completed without error.
So how do Comodo products work again...anything in their list of trusted digital signatures is allowed to run. I hope they dont trust their own digital signature.Comodo is now signing Locky ransomware binaries ~ Removed VirusTotal Results as per Policy ~
I think (at least I hope) TI was having fun with us. The Countersign, whether from Comodo, Symantec, DigiCert, GoDaddy, etc only guarantees that a file has been signed with a valid certificate and that the file has not been manipulated by anyone else prior to release. It by no means speaks to whether a file is malicious or not (and also- Northcat is not in the Comodo trusted Vendor list so would be treated like crap). The real issue here is how the previously valid certificate was obtained. Bribery and extortion are always very big, but my personal favorite is a Qakbot that targets software companies, the sole purpose of which is to harvest Private Signing keys. Of course an Outbound alerting firewall would have prevented the data acquisition by Qakbot, but this simple protection modality is often lost even for professionals.
CS-Comodo has been in this situation before.They have signed digital certificates for malware before and still do at times.Even if they are counter signers its concerns me as a comodo user... https://www.invincea.com/2015/10/dr...ers-and-employing-comodo-signed-certificates/
Hi TI! Seriously, the countersign just means that a certificate was issued by that authority to so-and-so and that all the necessary information and hoops that the software developer need to jump through were completed. It will also insure that any particular application signed with the original certificate was not manipulated after release. It does not in any way mean that the application is not malicious (sucks, I know. But this is the system the Powers-That-Be set up). Of the companies that dole out certificates, both Comodo and Symantec also produce security products (note that both Comodo and digiCert countersigned the application in your example above). This by NO MEANS should be understood that either company trusts such signed applications nor approves of the software firm that received the certificate! For instance, Symantec formerly gave approval via certificates to a software company run by Blackhats that sent out signed ransomware files. But although certificates were issued by and countersigned by them, Symantec/Norton still blocked the malware from day 1. The same can be said for Comodo. The signing and security businesses are totally separate! (ps- last week Symantec's app and Website certification biz was acquired by the firm Thoma Bravo for 1 BILLION USD. It will be merged with DigiCert). Anyway, please understand that I have GREAT RESPECT for you and in NO WAY want to minimize your concerns. So although I feel that worrying that riff-raffy software companies can get certificates and either produce malware or have certificates harvested by Blackhats is not a real issue, there is a Clear and Present danger that legitimate and well respected companies with demonstrated ties to a governmental Security Apparatus can use this trust to engage in Cyberwarfare to the detriment of us all. Previous (traitorous) administrations blew this off as of no consequence, but Thank God Almighty this is no longer the case which is why I am back in the fold.
Hey CS, Thanks for the heads up! You can see in one of screenshots where comodo was the signer and digiCERT the counter signer.While these incidents seem to more happening with comodo than symantec its a constant downside when their name is constantly being used by bad guys. While I have to agree with what you say.Doesnt Comodo have their own certificate whitelisted? I am concerned if anyone ever comes across such binaries will comodo isolate them or let them run?? I am not sure what makes you think that I feel you don't respect me.Hey! Its mutual girlie! By no means what you said disrespected me or anyone you were stating what was needed to be nothing wrong with contradicting or critizing me as far as its civil and constructive.....this was informative so thankyou....Everyone has flaws...we learn from each other.The respect is mutual old friend.... Also not sure what you meant by leaving the fold,your contributions and posts are well valued.I am mere mortal
Hi all https://forums.comodo.com/beta-corner-cis/comodo-internet-security-v10026346-beta-t120645.0.html Comodo Internet Security 10.0.2.6346 - Beta With best Regards Mops21
Hi all https://forums.comodo.com/beta-corner-cis/comodo-internet-security-v10026382-beta3-t120767.0.html Comodo Internet Security v 10.0.2.6382 - Beta3 With best Regards Mops21
Hi all https://forums.comodo.com/beta-corner-cis/comodo-internet-security-v10026392-rc-t120807.0.html Comodo Internet Security v10.0.2.6392 - RC With best Regards Mops21
Hi all Comodo Internet Security v10.0.2.6396 - RC https://forums.comodo.com/beta-corner-cis/comodo-internet-security-v10026396-rc-t120836.0.html With best Regards Mops21
Hi all Comodo Internet Security v10.0.2.6396 Releases https://forums.comodo.com/news-anno...et-security-v10026396-released-t120847.0.html With best Regards Mops21
I tried installing Comodo Firewall on a new workstation that I was setting up. I have two docks for hotswap ESATA disks, and it seems that CFW prevents ejecting the disks. Task manager does not show any open file handles, but trying to eject the disks pops up the usual "Windows is unable to stop the device..." error message. Event Viewer reveals a System event 225 which states that "cmdagent.exe stopped the removal or ejection for the device". Disabling every protection and even stopping the whole CFW from the taskbar icon does not stop cmdagent process. I wonder if anyone knows a way to overcome this problem...
Still waiting for the internal updater to recognize the new version (6 days later). Edit: Still on 10.0.1.6294, and still say 'Up to date' after 8 days, is this delay normal?
Hi all Comodo Internet Security v 10.0.2.6406 - RC https://forums.comodo.com/beta-corner-cis/comodo-internet-security-v10026406-rc-t120907.0.html With best Regards Mops21
Hi all Comodo Internet Security v 10.0.2.6408 - RC https://forums.comodo.com/beta-corner-cis/comodo-internet-security-v10026408-rc-t120932.0.html With best Regards Mops21