Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Comodo
Comodo CIS Bug fix policy
Message
<blockquote data-quote="bazang" data-source="post: 1102432" data-attributes="member: 114717"><p>It is a common issue across the entire IT and software development industries. It is not unique to Comodo. Neither is it a result of Comodo negligence or disregard for the product. Unless an organization or person is particularly obsessive-compulsive about tracking certificate expiration dates (and most are not OCD about it), it is easy to lose track and you have an expired certificate problem.</p><p></p><p>There are those here that want to blow the certificate problem way out of proportion, mis-characterize it and say things about it that just ain't true, and use it as "just another example of Comodo not caring for end users" - and meanwhile those detractors never paid a single cent for the Comodo product. They never donated a single cent to support the development of the product. They argue "If you place it onto the market, then you - as the owner - are obligated to make it trouble-free." That is not how it works. Those detractors are 100% incorrect. The product owner owes nobody anything. He can decide that he wants to maintain the product at the level of pig slop quality - and if you do not like it then get lost. Go use something else.</p><p></p><p>And to clarify, Melih remains the owner of all Comodo products. He decides what level of software quality is good enough. Not end users.</p></blockquote><p></p>
[QUOTE="bazang, post: 1102432, member: 114717"] It is a common issue across the entire IT and software development industries. It is not unique to Comodo. Neither is it a result of Comodo negligence or disregard for the product. Unless an organization or person is particularly obsessive-compulsive about tracking certificate expiration dates (and most are not OCD about it), it is easy to lose track and you have an expired certificate problem. There are those here that want to blow the certificate problem way out of proportion, mis-characterize it and say things about it that just ain't true, and use it as "just another example of Comodo not caring for end users" - and meanwhile those detractors never paid a single cent for the Comodo product. They never donated a single cent to support the development of the product. They argue "If you place it onto the market, then you - as the owner - are obligated to make it trouble-free." That is not how it works. Those detractors are 100% incorrect. The product owner owes nobody anything. He can decide that he wants to maintain the product at the level of pig slop quality - and if you do not like it then get lost. Go use something else. And to clarify, Melih remains the owner of all Comodo products. He decides what level of software quality is good enough. Not end users. [/QUOTE]
Insert quotes…
Verification
Post reply
Top