<?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: Google&#8217;s &#8216;Chrome&#8217; released&#8230;</title>
	<atom:link href="http://www.samurainet.org/blog/2008/09/03/googles-chrome-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.samurainet.org/blog/2008/09/03/googles-chrome-released/</link>
	<description>"If you cut me, I bleed binary"</description>
	<pubDate>Tue, 06 Jan 2009 23:04:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Daniel</title>
		<link>http://www.samurainet.org/blog/2008/09/03/googles-chrome-released/#comment-396</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Wed, 03 Sep 2008 19:17:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.samurainet.org/blog/?p=41#comment-396</guid>
		<description>I can't remember where the article was (try Ars Technica?) but the exploit is because Google used an older version of WebKit that did not have the fix for this vulnerability.

The article went on to mention the history of the exploit and how Apple downplayed the seriousness of the issue and took close to 3 months to patch it.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t remember where the article was (try Ars Technica?) but the exploit is because Google used an older version of WebKit that did not have the fix for this vulnerability.</p>
<p>The article went on to mention the history of the exploit and how Apple downplayed the seriousness of the issue and took close to 3 months to patch it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
