<?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: Is Your SSL Certificate Signed Using Vulnerable MD5?</title>
	<atom:link href="http://hostingfu.com/article/your-ssl-certificates-signed-using-vulnerable-md5/feed" rel="self" type="application/rss+xml" />
	<link>http://hostingfu.com/article/your-ssl-certificates-signed-using-vulnerable-md5</link>
	<description>Web Hosting Blog by a Software Developer</description>
	<lastBuildDate>Fri, 02 Jul 2010 10:59:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: beamq</title>
		<link>http://hostingfu.com/article/your-ssl-certificates-signed-using-vulnerable-md5/comment-page-1#comment-970</link>
		<dc:creator>beamq</dc:creator>
		<pubDate>Thu, 30 Jul 2009 03:00:17 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=179#comment-970</guid>
		<description>&lt;p&gt;Most of our sites are using MD5.  What can we do ? &lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Most of our sites are using MD5.  What can we do ? </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://hostingfu.com/article/your-ssl-certificates-signed-using-vulnerable-md5/comment-page-1#comment-969</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 05 Jan 2009 17:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=179#comment-969</guid>
		<description>&lt;p&gt;The problem is, it doesn&#039;t matter so much that your site uses SHA1 - if any registrar, anywhere, uses MD5, then your site (which is happily using a SHA1 cert on a sane registrar) can be spoofed. In fact, your site using MD5 isn&#039;t really useful - if you read the attack paper, they need to predict the serial number of the certificate some time ahead in order to produce the so-called &#039;birthday block&#039; that they need to convince the CA to embed into the certificate.&lt;/p&gt;
&lt;p&gt;So, as a user, you should tell your browser not to trust MD5. And as a webmaster, you should make sure you&#039;re not using MD5, because it won&#039;t be long before browsers stop accepting it. But it&#039;s not about &#039;safety&#039; for the website itself; until browsers lock down MD5, &lt;em&gt;everyone&lt;/em&gt; is vulnerable.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>The problem is, it doesn&#8217;t matter so much that your site uses SHA1 &#8211; if any registrar, anywhere, uses MD5, then your site (which is happily using a SHA1 cert on a sane registrar) can be spoofed. In fact, your site using MD5 isn&#8217;t really useful &#8211; if you read the attack paper, they need to predict the serial number of the certificate some time ahead in order to produce the so-called &#8216;birthday block&#8217; that they need to convince the CA to embed into the certificate.</p>
<p>So, as a user, you should tell your browser not to trust MD5. And as a webmaster, you should make sure you&#8217;re not using MD5, because it won&#8217;t be long before browsers stop accepting it. But it&#8217;s not about &#8216;safety&#8217; for the website itself; until browsers lock down MD5, <em>everyone</em> is vulnerable.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
