<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Open Source Code Contains Security Holes</title>
	<atom:link href="http://jeremy.linuxquestions.org/2008/01/10/open-source-code-contains-security-holes/feed/" rel="self" type="application/rss+xml" />
	<link>http://jeremy.linuxquestions.org/2008/01/10/open-source-code-contains-security-holes/</link>
	<description>Open Source > Linux > LQ</description>
	<lastBuildDate>Fri, 24 Jul 2009 01:02:52 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jeremy</title>
		<link>http://jeremy.linuxquestions.org/2008/01/10/open-source-code-contains-security-holes/comment-page-1/#comment-1790</link>
		<dc:creator>jeremy</dc:creator>
		<pubDate>Mon, 21 Jan 2008 15:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://jeremy.linuxquestions.org/2008/01/10/open-source-code-contains-security-holes/#comment-1790</guid>
		<description>I wouldn&#039;t say that defects per line of code is *completely* irrelevant, but you certainly need to take it for what it is... and nothing more.  Generally speaking, less defects should mean less vulnerabilities and also less critical vulnerabilities.  Of course, specific cases may very, but I think the track record of the projects mentioned bares out this general case.

--jeremy</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t say that defects per line of code is *completely* irrelevant, but you certainly need to take it for what it is&#8230; and nothing more.  Generally speaking, less defects should mean less vulnerabilities and also less critical vulnerabilities.  Of course, specific cases may very, but I think the track record of the projects mentioned bares out this general case.</p>
<p>&#8211;jeremy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dysk</title>
		<link>http://jeremy.linuxquestions.org/2008/01/10/open-source-code-contains-security-holes/comment-page-1/#comment-1789</link>
		<dc:creator>dysk</dc:creator>
		<pubDate>Mon, 21 Jan 2008 01:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://jeremy.linuxquestions.org/2008/01/10/open-source-code-contains-security-holes/#comment-1789</guid>
		<description>Neat article, however defects per line of code is somewhat of an irrelevant benchmark.  For one, lines of code is only a measure of a program&#039;s complexity in the broadest sense, and one remotely accessible vulnerability is enough to leave you in serious trouble.

For another, the number of defects entirely leaves out the severity of each defect, as by this metric a remotely exploitable root code execution defect gets the same weight as the use of an uninitialized variable.</description>
		<content:encoded><![CDATA[<p>Neat article, however defects per line of code is somewhat of an irrelevant benchmark.  For one, lines of code is only a measure of a program&#8217;s complexity in the broadest sense, and one remotely accessible vulnerability is enough to leave you in serious trouble.</p>
<p>For another, the number of defects entirely leaves out the severity of each defect, as by this metric a remotely exploitable root code execution defect gets the same weight as the use of an uninitialized variable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremy</title>
		<link>http://jeremy.linuxquestions.org/2008/01/10/open-source-code-contains-security-holes/comment-page-1/#comment-1780</link>
		<dc:creator>jeremy</dc:creator>
		<pubDate>Wed, 16 Jan 2008 00:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://jeremy.linuxquestions.org/2008/01/10/open-source-code-contains-security-holes/#comment-1780</guid>
		<description>Well, that&#039;s part of the issue.  Numbers like that are not usually available for proprietary software, since the code to run the tests is not openly available.  Even if a company gave the source to Coverity to test for internal knowledge, they would almost never publicly release the numbers.

--jeremy</description>
		<content:encoded><![CDATA[<p>Well, that&#8217;s part of the issue.  Numbers like that are not usually available for proprietary software, since the code to run the tests is not openly available.  Even if a company gave the source to Coverity to test for internal knowledge, they would almost never publicly release the numbers.</p>
<p>&#8211;jeremy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rshame</title>
		<link>http://jeremy.linuxquestions.org/2008/01/10/open-source-code-contains-security-holes/comment-page-1/#comment-1779</link>
		<dc:creator>rshame</dc:creator>
		<pubDate>Tue, 15 Jan 2008 12:36:53 +0000</pubDate>
		<guid isPermaLink="false">http://jeremy.linuxquestions.org/2008/01/10/open-source-code-contains-security-holes/#comment-1779</guid>
		<description>jeremy,

I&#039;d like to ask you to introduce (if you have them) the numbers of defect rate in non-Open Source software for the sake of healthy comparison. Obviously to the reader numbers such as .127 per thousand lines sound bold: they sound to me as no defective at all. I&#039;ll starve to know how much the defect rate sounds for a - for instance - Microsoft software. Do you have this? Great article, by the way, thanks a lot for sharing.</description>
		<content:encoded><![CDATA[<p>jeremy,</p>
<p>I&#8217;d like to ask you to introduce (if you have them) the numbers of defect rate in non-Open Source software for the sake of healthy comparison. Obviously to the reader numbers such as .127 per thousand lines sound bold: they sound to me as no defective at all. I&#8217;ll starve to know how much the defect rate sounds for a &#8211; for instance &#8211; Microsoft software. Do you have this? Great article, by the way, thanks a lot for sharing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
