<?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: SSL exploit turns Firefox into malware distributor</title>
	<atom:link href="http://www.formortals.com/ssl-exploit-turns-firefox-into-malware-distributor/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.formortals.com/ssl-exploit-turns-firefox-into-malware-distributor/</link>
	<description>Because technology isn&#039;t just for geeks</description>
	<lastBuildDate>Tue, 24 Jan 2012 20:02:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Programming news: Firefox SSL flaw, Rails BugMash event, browser compatibility on Digg &#124; Programming and Development &#124; TechRepublic.com</title>
		<link>http://www.formortals.com/ssl-exploit-turns-firefox-into-malware-distributor/comment-page-1/#comment-2016</link>
		<dc:creator>Programming news: Firefox SSL flaw, Rails BugMash event, browser compatibility on Digg &#124; Programming and Development &#124; TechRepublic.com</dc:creator>
		<pubDate>Tue, 04 Aug 2009 05:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.formortals.com/?p=648#comment-2016</guid>
		<description>[...] all?) unnamed Certificate Authority (CA) validates the domain name in SSL certificate creation, Firefox is vulnerable to a flaw that tricks it into accepting valid SSL certificates issued to other.... At the heart of the matter is that the CA(s) are allowing certificate requests to be processed [...]</description>
		<content:encoded><![CDATA[<p>[...] all?) unnamed Certificate Authority (CA) validates the domain name in SSL certificate creation, Firefox is vulnerable to a flaw that tricks it into accepting valid SSL certificates issued to other&#8230;. At the heart of the matter is that the CA(s) are allowing certificate requests to be processed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Ou</title>
		<link>http://www.formortals.com/ssl-exploit-turns-firefox-into-malware-distributor/comment-page-1/#comment-1964</link>
		<dc:creator>George Ou</dc:creator>
		<pubDate>Fri, 31 Jul 2009 18:26:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.formortals.com/?p=648#comment-1964</guid>
		<description>It&#039;s not just open source.  Everyone screwed this implementation of X.509 up including Microsoft Crypto API and just about every other implementation of SSL.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not just open source.  Everyone screwed this implementation of X.509 up including Microsoft Crypto API and just about every other implementation of SSL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nucrash</title>
		<link>http://www.formortals.com/ssl-exploit-turns-firefox-into-malware-distributor/comment-page-1/#comment-1955</link>
		<dc:creator>nucrash</dc:creator>
		<pubDate>Fri, 31 Jul 2009 12:28:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.formortals.com/?p=648#comment-1955</guid>
		<description>Well, that&#039;s a failing by Open Source.  I would hope to see an update, but would be afraid to use the auto update tool of FF.  :/</description>
		<content:encoded><![CDATA[<p>Well, that&#8217;s a failing by Open Source.  I would hope to see an update, but would be afraid to use the auto update tool of FF.  :/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Ou</title>
		<link>http://www.formortals.com/ssl-exploit-turns-firefox-into-malware-distributor/comment-page-1/#comment-1941</link>
		<dc:creator>George Ou</dc:creator>
		<pubDate>Thu, 30 Jul 2009 22:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.formortals.com/?p=648#comment-1941</guid>
		<description>&lt;a href=&quot;#comment-1936&quot; rel=&quot;nofollow&quot;&gt;@Justin James &lt;/a&gt; 

Well, the CAs use OpenSSL which does not treat NULL CHAR as an end of string.  The clients on the other hand such as Crypto API do treat NULL CHAR as end of string.  That&#039;s your disconnect right there.

Now the CAs can probably change their signing application to reject anything with a NULL CHAR in the subject line which would probably make sense since there&#039;s no reason to have a character that the DNS system doesn&#039;t recognize anyways.</description>
		<content:encoded><![CDATA[<p><a href="#comment-1936" rel="nofollow">@Justin James </a> </p>
<p>Well, the CAs use OpenSSL which does not treat NULL CHAR as an end of string.  The clients on the other hand such as Crypto API do treat NULL CHAR as end of string.  That&#8217;s your disconnect right there.</p>
<p>Now the CAs can probably change their signing application to reject anything with a NULL CHAR in the subject line which would probably make sense since there&#8217;s no reason to have a character that the DNS system doesn&#8217;t recognize anyways.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin James</title>
		<link>http://www.formortals.com/ssl-exploit-turns-firefox-into-malware-distributor/comment-page-1/#comment-1936</link>
		<dc:creator>Justin James</dc:creator>
		<pubDate>Thu, 30 Jul 2009 18:52:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.formortals.com/?p=648#comment-1936</guid>
		<description>That is a truly nasty bug. Great question... why would a CA sign a cert with a domain name that is not a valid domain name? Once again, poor programming...

J.Ja</description>
		<content:encoded><![CDATA[<p>That is a truly nasty bug. Great question&#8230; why would a CA sign a cert with a domain name that is not a valid domain name? Once again, poor programming&#8230;</p>
<p>J.Ja</p>
]]></content:encoded>
	</item>
</channel>
</rss>

