Open Source Risks and Responsibilities
Linked by Mark Tolliver on Thu 13th Sep 2007 08:14 UTC
Editorial The widespread acceptance of open source continues to grow as a cost-effective alternative to traditional network deployments. Well-known projects such as Linux have proven themselves to be in the enterprise environment, helping to dispel the fear, uncertainty and doubt preceding open source implementations. In the past two years, the industry has begun to shift from a total dependence on proprietary applications to a desire for more cost-effective, scalable and collaborative solutions.
E-mail Print r 0   · Read More · 22 Comment(s) http://osne.ws/ecy
Permalink for comment 271064
To read all comments associated with this story, please click here.
Response times
by sappyvcv on Thu 13th Sep 2007 15:23 UTC
sappyvcv
Member since:
2005-07-06

Pointing to the thousands of open source contributors on any given project, developers note that any discovered vulnerability is likely to be fixed within hours, whereas a security flaw in a proprietary application may not be fixed for several days depending on the backlog.

There's usually a reason for that. For important security flaws, they'll fix it right away, but they need to do regression testing, determine if the same flaw exists elsewhere, etc. It's not just a quick hack and they're happy.

Reply Score: 2