<?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: MD5 Weaknesses Could Lead to Certificate Forgery</title>
	<atom:link href="http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/</link>
	<description></description>
	<lastBuildDate>Thu, 19 Nov 2009 15:36:11 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: WEB Consultant</title>
		<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/comment-page-1/#comment-103636</link>
		<dc:creator>WEB Consultant</dc:creator>
		<pubDate>Mon, 26 Jan 2009 06:34:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=62#comment-103636</guid>
		<description>MD5 hash algorithm is very old. I think security specialists have to develop something more usefull and strong.</description>
		<content:encoded><![CDATA[<p>MD5 hash algorithm is very old. I think security specialists have to develop something more usefull and strong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: event security</title>
		<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/comment-page-1/#comment-103622</link>
		<dc:creator>event security</dc:creator>
		<pubDate>Mon, 26 Jan 2009 01:52:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=62#comment-103622</guid>
		<description>@Wanda: I think that was just an intermittent error with Facebook that should have resolved itself.</description>
		<content:encoded><![CDATA[<p>@Wanda: I think that was just an intermittent error with Facebook that should have resolved itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wanda R</title>
		<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/comment-page-1/#comment-103449</link>
		<dc:creator>Wanda R</dc:creator>
		<pubDate>Fri, 23 Jan 2009 02:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=62#comment-103449</guid>
		<description>I&#039;m not an IT person, just a regular user. I recently switched to Firefox which is quicker and sleeker. Now, all day today, when I try to enter the Facebook application, I get the following...Secure Connection Failed.     
      
An error occurred during a connection to login.facebook.com.

Can&#039;t connect securely because the SSL protocol has been disabled.

(Error code: ssl_error_ssl_disabled)

The page you are trying to view can not be shown because the authenticity of the received data could not be verified.

    * Please contact the web site owners to inform them of this problem.

What should I do? I can get in with IE but that is sooo sloow. HELP.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not an IT person, just a regular user. I recently switched to Firefox which is quicker and sleeker. Now, all day today, when I try to enter the Facebook application, I get the following&#8230;Secure Connection Failed.     </p>
<p>An error occurred during a connection to login.facebook.com.</p>
<p>Can&#8217;t connect securely because the SSL protocol has been disabled.</p>
<p>(Error code: ssl_error_ssl_disabled)</p>
<p>The page you are trying to view can not be shown because the authenticity of the received data could not be verified.</p>
<p>    * Please contact the web site owners to inform them of this problem.</p>
<p>What should I do? I can get in with IE but that is sooo sloow. HELP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johnathan Nightingale</title>
		<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/comment-page-1/#comment-103307</link>
		<dc:creator>Johnathan Nightingale</dc:creator>
		<pubDate>Wed, 21 Jan 2009 19:31:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=62#comment-103307</guid>
		<description>@Nick, and others asking similar questions:

We certainly can look at retiring MD5 as a supported algorithm, in fact that discussion is already happening in the mozilla.dev.tech.crypto newsgroup, and the bugs are being worked on.  As you anticipate, the decision will need to take into account how much of the internet it breaks.  I&#039;ve got a related post up about how to answer some of those questions, here: 

http://blog.johnath.com/2009/01/21/ssl-information-wants-to-be-free/</description>
		<content:encoded><![CDATA[<p>@Nick, and others asking similar questions:</p>
<p>We certainly can look at retiring MD5 as a supported algorithm, in fact that discussion is already happening in the mozilla.dev.tech.crypto newsgroup, and the bugs are being worked on.  As you anticipate, the decision will need to take into account how much of the internet it breaks.  I&#8217;ve got a related post up about how to answer some of those questions, here: </p>
<p><a href="http://blog.johnath.com/2009/01/21/ssl-information-wants-to-be-free/" rel="nofollow">http://blog.johnath.com/2009/01/21/ssl-information-wants-to-be-free/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pakman</title>
		<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/comment-page-1/#comment-103065</link>
		<dc:creator>pakman</dc:creator>
		<pubDate>Sun, 18 Jan 2009 16:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=62#comment-103065</guid>
		<description>find more at grc.com/securitynow
Breaking SSL, PDP-8&#039;s &amp; UltraCapacitors episode 177

a security podcast

download

http://media.grc.com/sn/sn-177-lq.mp3</description>
		<content:encoded><![CDATA[<p>find more at grc.com/securitynow<br />
Breaking SSL, PDP-8&#8217;s &amp; UltraCapacitors episode 177</p>
<p>a security podcast</p>
<p>download</p>
<p><a href="http://media.grc.com/sn/sn-177-lq.mp3" rel="nofollow">http://media.grc.com/sn/sn-177-lq.mp3</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Mentré</title>
		<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/comment-page-1/#comment-102868</link>
		<dc:creator>David Mentré</dc:creator>
		<pubDate>Thu, 15 Jan 2009 10:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=62#comment-102868</guid>
		<description>Hello,

This security issue shows that the security model of Firefox relying exclusively on third party authentication (i.e. the recent demise of self-signed certificates in Firefox 3) is fundamentally broken.

One should not be more confident in a Verisign certificate than in a self-signed one. What is really meaningful is when something &quot;strange&quot; happens in the background, e.g. when a website changes its certificate (self-signed or not).

Sincerely yours,
David Mentré</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>This security issue shows that the security model of Firefox relying exclusively on third party authentication (i.e. the recent demise of self-signed certificates in Firefox 3) is fundamentally broken.</p>
<p>One should not be more confident in a Verisign certificate than in a self-signed one. What is really meaningful is when something &#8220;strange&#8221; happens in the background, e.g. when a website changes its certificate (self-signed or not).</p>
<p>Sincerely yours,<br />
David Mentré</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom K</title>
		<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/comment-page-1/#comment-102140</link>
		<dc:creator>Tom K</dc:creator>
		<pubDate>Sun, 04 Jan 2009 19:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=62#comment-102140</guid>
		<description>How about steps to check whether a cert in the chain uses MD5? An advisory concerning Moz. Products like firefox would be nice! Firefox extension that warns when an https connection relying on a MD5 hashed cert is established?

Please take some real steps instead of only copy and pasting the link here. The advice &quot;have caution&quot; is really laughable, how shall i know what to look for if you don&#039;t tell me?</description>
		<content:encoded><![CDATA[<p>How about steps to check whether a cert in the chain uses MD5? An advisory concerning Moz. Products like firefox would be nice! Firefox extension that warns when an https connection relying on a MD5 hashed cert is established?</p>
<p>Please take some real steps instead of only copy and pasting the link here. The advice &#8220;have caution&#8221; is really laughable, how shall i know what to look for if you don&#8217;t tell me?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kasper</title>
		<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/comment-page-1/#comment-101957</link>
		<dc:creator>Kasper</dc:creator>
		<pubDate>Thu, 01 Jan 2009 22:11:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=62#comment-101957</guid>
		<description>I came here hoping to find an official answer to whether setting the security.ssl3.rsa_rc4_128_md5 option to false is sufficient to protect yourself against this weakness.</description>
		<content:encoded><![CDATA[<p>I came here hoping to find an official answer to whether setting the security.ssl3.rsa_rc4_128_md5 option to false is sufficient to protect yourself against this weakness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven</title>
		<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/comment-page-1/#comment-101930</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Thu, 01 Jan 2009 13:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=62#comment-101930</guid>
		<description>Firefox can patch this vulnerability very quickly and very easily (show the world how quickly a Firefox can mitigate the issue!) using the existing SSL verification mechanisms for example: (xxx website uses an insecure security certificate. The certificate is not trusted because the issuer certificate uses the insecure MD5 algorithm. Error code: sec_error_insecure_MD5_issuer_certificate))

Users can still add an exception to the Rule if needed but it would Mitigate the issue because the user would still be warned...It would also put more pressure on affected websites still using MD5 certificates to update them immediately and further mitigate any attack scenarios...

The amount of websites using MD5 based certificates are small and if they see their certificate not working with Firefox or showing the &quot;Secure Connection Failed&quot; Page they will request a new certificate immediately...

The longer Browsers accept MD5 based certificates the longer it will take to force website operators to update as some people just wouldn&#039;t care unless their certificate no longer works...</description>
		<content:encoded><![CDATA[<p>Firefox can patch this vulnerability very quickly and very easily (show the world how quickly a Firefox can mitigate the issue!) using the existing SSL verification mechanisms for example: (xxx website uses an insecure security certificate. The certificate is not trusted because the issuer certificate uses the insecure MD5 algorithm. Error code: sec_error_insecure_MD5_issuer_certificate))</p>
<p>Users can still add an exception to the Rule if needed but it would Mitigate the issue because the user would still be warned&#8230;It would also put more pressure on affected websites still using MD5 certificates to update them immediately and further mitigate any attack scenarios&#8230;</p>
<p>The amount of websites using MD5 based certificates are small and if they see their certificate not working with Firefox or showing the &#8220;Secure Connection Failed&#8221; Page they will request a new certificate immediately&#8230;</p>
<p>The longer Browsers accept MD5 based certificates the longer it will take to force website operators to update as some people just wouldn&#8217;t care unless their certificate no longer works&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Covington</title>
		<link>http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/comment-page-1/#comment-101910</link>
		<dc:creator>Gary Covington</dc:creator>
		<pubDate>Thu, 01 Jan 2009 04:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/security/?p=62#comment-101910</guid>
		<description>How do I as a user tell if the certificate is MD5 or later?  The little &quot;locked padlock&quot; symbol doesn&#039;t say.</description>
		<content:encoded><![CDATA[<p>How do I as a user tell if the certificate is MD5 or later?  The little &#8220;locked padlock&#8221; symbol doesn&#8217;t say.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
