<?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"
	>
<channel>
	<title>Comments on: Red Hat Certificate System now open source</title>
	<atom:link href="http://securitymusings.com/article/260/red-hat-certificate-system-now-open-source/feed" rel="self" type="application/rss+xml" />
	<link>http://securitymusings.com/article/260/red-hat-certificate-system-now-open-source</link>
	<description>Rants and raves from information security professionals</description>
	<pubDate>Thu, 20 Nov 2008 16:30:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Scott Shorter</title>
		<link>http://securitymusings.com/article/260/red-hat-certificate-system-now-open-source#comment-103</link>
		<dc:creator>Scott Shorter</dc:creator>
		<pubDate>Thu, 20 Mar 2008 20:01:19 +0000</pubDate>
		<guid isPermaLink="false">http://securitymusings.com/article/260/red-hat-certificate-system-now-open-source#comment-103</guid>
		<description>	&lt;p&gt;I&#8217;m curious how long it will be until it shows up as a debian package.&lt;/p&gt;

	&lt;p&gt;Open source of course doesn&#8217;t mean secure or easy to use, it just increases the avenues for scrutiny of the software.  I&#8217;ve seen plenty of open source projects where you need to spend a long time learning the system because of the poor documentation &#8211; that lack of documentation will be an impediment to any effort to obtain assurance in the security of the system.&lt;/p&gt;

	&lt;p&gt;OpenSSL is a fine example of open source software for which vulnerabilities continue to be found and fixed.  The Bleichenbacher vulnerability (http://www.matasano.com/log/469/many-rsa-signatures-may-be-forgeable-in-openssl-and-elsewhere/) is not something that any amount of testing would have uncovered, until the nature of the exploit was known.&lt;/p&gt;

	&lt;p&gt;Finally, several years ago when &lt;span class="caps"&gt;NSS&lt;/span&gt; was opened up I remember talking to our friend TP about it &#8211; I asked if his agency or the DoD were likely to object, celebrate, or even notice the fact that the server was opened up &#8211; the best guess was &#8220;not even notice&#8221;.  It&#8217;s been almost a decade since then, I wonder if agencies pay any more attention to such questions now.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>I&#8217;m curious how long it will be until it shows up as a debian package.</p>
<p>Open source of course doesn&#8217;t mean secure or easy to use, it just increases the avenues for scrutiny of the software.  I&#8217;ve seen plenty of open source projects where you need to spend a long time learning the system because of the poor documentation &#8211; that lack of documentation will be an impediment to any effort to obtain assurance in the security of the system.</p>
<p>OpenSSL is a fine example of open source software for which vulnerabilities continue to be found and fixed.  The Bleichenbacher vulnerability (http://www.matasano.com/log/469/many-rsa-signatures-may-be-forgeable-in-openssl-and-elsewhere/) is not something that any amount of testing would have uncovered, until the nature of the exploit was known.</p>
<p>Finally, several years ago when <span class="caps">NSS</span> was opened up I remember talking to our friend TP about it &#8211; I asked if his agency or the DoD were likely to object, celebrate, or even notice the fact that the server was opened up &#8211; the best guess was &#8220;not even notice&#8221;.  It&#8217;s been almost a decade since then, I wonder if agencies pay any more attention to such questions now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
