yes, of course, i’m preparing fireworks
Replacing a failed certificate can be a complex process for a number of reasons:
-
[Validation and Authorisation: Comodo needs to obtain new authorisation and validation for the certificate, which can take time
-
[Development and Testing: Once the new certificate has been obtained, it must be integrated into the software, followed by rigorous testing to ensure that it works correctly without introducing new vulnerabilities
-
[Compatibility: It must be ensured that the new certificate is compatible with all versions of the software and the different operating systems used by customers
These steps are necessary to ensure that the software remains secure and reliable. Comodo is probably working on these aspects to resolve the problem once and for all. -
[Distribution: The update must then be distributed to all users, which can be a major logistical process
I am not able to Download Comodo at all. I get “7za.dll wasn’t properly signed. Installation Aborted”
1 Like
@D.Andreas Personally, I feel that Comodo doesn’t want people to use its CIS product anymore because it’s incredible that a certification issue has taken the company more than 1.5 months to fix nothing. Furthermore, the same issue had already been fixed in the enterprise version XCS a week ago. But no action on the CIS product.
I suggest using another antivirus alternative to keep your cyber security and protect your data from viruses.
2 Likes
Quite the contrary!
I’ll say this:
Look at how long the company and the product have been around.
Look at how long the boss has been the same.
Look at the fact that on this forum the company’s stakeholders have been the same for a very long time.
You won’t find that anywhere else.
This means that everything is being done to make the situation sustainable and that the word loyalty really means something at Comodo.
At Comodo, we think in the long term.
On the other hand, take a look at Microsoft, which releases bug-ridden Windows updates every time, and every month corrects those bugs with new ones! How many BSOD at Microsoft because of updates?
Hurrying is not always the right solution.
Especially when you depend on others.
If you want, you can already test Comodo CIS Pro with a previous version not affected by the certificate problem.
On the other hand, I wouldn’t recommend Xcitium: it’s far too expensive!
Those who want to do, do it; those who don’t want to do, look for an excuse not to do it.
1 Like
Dear Xéno, I understand your decision to change product and move to another company; it’s a personal and individual choice that I respect, as do you… 
But I don’t understand why you don’t express your enthusiasm on the forum for your new product, rather than the repeated denigration on Comodo’s forum.
Your comments are no longer relevant to the subject of this forum, and this one in particular. (Certificats problem)
It’s not very nice to come here and spread discouragement. The Comodo teams and those who love and use Comodo could be offended by this redundant and sarcastic behaviour.
Comodo CIS Pro is the only security software that has saved me from many infections over the years. It is so powerful that we can recommend an older version without putting people at risk.
It’s your right not to like it. But I’m sure you can also declare your love for your new security suite on its forum 
It’s based on a good feeling and common sense!
I have never written anywhere that I changed the product, etc. I have been using Comodo since 2006.
Your comments are also not relevant to the topic of this forum, just flood.
And criticism is an incentive to improve work efficiency.
2 Likes
Hello my friend! 
Sorry, I misinterpreted Xéno, this, like some of your last comments, seemed rather mocking and sarcastic…
“news? it’s 3 of october and time is ticking 
”
“christmas is coming!! And after that easter 
”
“jump on another train”
“another week passed 
”
“i i said multiple time. The fix will come at the end of the year”
“just few months and it will be ready, don’t rush please”
“hello, another day passed. The issue will be resolved 21 days ago”
“Those who want to do, do it; those who don’t want to do, look for an excuse not to do it.”
Putting pressure on developers, if I could do it, I stopped.
I’m trying to get the message across, because this is a profession where there are a lot of burn-outs…
As you’ve been here for a long time, let’s all pull together with the whole team!
Let’s avoid annoying them - I can assure you it can have a positive influence!
But I realise that we’re straying from the main subject. It was just an encouragement to fight together for the right cause.
I’m going to stop commenting for a while.
I’m supporting the whole Comodo team!
Trust me I doubt the developers read this forum or give it any more than a casual glance.
1 Like
- Overclocker-001, your 2-nd nick - Melih?
- As for deviations from the topic, the topic is devoted to the revocation of the network and its long return. Xeno and other users write about this. But you deviated from the topic - you started singing CIS’s praises. There are other places for this.
- We all love CIS, that’s why we’re sitting here and waiting for the problem with the certificate to be fixed. But this does not happen for a very long time, an unnaturally long time. And there are no clear explanations for the long-term solution to the problem.
And here you started telling us tales about “bad and expensive other antiviruses” (which, by the way, are used by billions of people!). Did they pay you money for this? You should be ashamed of your inappropriate conversations in this thread, as if everything is fine with the Comodo team…
4 Likes
I don’t know if others can see it, but a message appeared above my comment from no one (I quote):
No overclocker 001 isn’t Melih.
I know. From my side it was an ironic remark… Although who knows…
@Xao_Fan-Tzilin Same here.
1 Like
Messages that appear above a post (and that have a “Person with shield” icon) are publicly visible notations regarding your post that are made by the moderators or the Comodo staff. In your case, the message above your post (“No overclocker 001 isn’t Melih”) was added to clarify your comments. It can be very difficult for other users to perceive sarcasm from text alone because the usual clues that suggest sarcasm (such as facial expressions and vocal inflections) are absent. So, other users could perceive your comments as fact rather than as sarcasm. Thus, the moderators added a notation of fact to prevent any confusion.
5 Likes
- Obtaining a new certificate for signing an application is a fast and easy process, doesn’t require months of wait and if the entity that makes the request is already known to the certificate issuer it is almost immediate. (Not even mentioning that in this case the company was also one of main certificate issuers that now splitted its division to Sectigo, and you can still get new signing certificates from them, that makes the thing order of magnitude more grotesque.)
2\3) A valid certificate signing if previous is no more valid because expired or revoked, doesn’t need to be tested for compatibility, or new bugs, it is just a signature with one of the common standardized formats\algorithms, that is used to ensure that it hasn’t been tampered by unauthorized people. If it is revoked because unauthorized people were able to have access to private key, it is needed only to require a new signing key and recompile the same source code with new key as is always done in these cases without leaving software without valid certificate for so long. If they don’t do it this, certainly this isn’t caused by the fact it requires much time to sign it again with a valid certificate.
- Logistic problem to distribute it? LOL this is funny… They haven’t to distribute CIS door to door with a delivery boy.
2 Likes
What exactly made microsoft revoke the certificate in the first place?
This has nothing to do with Microsoft.
No one has said what really happened yet, and it won’t be said.
1 Like
How do you know for sure? Since in your own words.
Just playing devil’s advocate…