<?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: How to crash Google Chrome</title>
	<atom:link href="http://www.root777.com/security-vulnerability/how-to-crash-google-chrome/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.root777.com/security-vulnerability/how-to-crash-google-chrome/</link>
	<description>Computer Security &#38; Technology</description>
	<lastBuildDate>Mon, 12 Jul 2010 22:19:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Daniel McDicken</title>
		<link>http://www.root777.com/security-vulnerability/how-to-crash-google-chrome/comment-page-1/#comment-1944</link>
		<dc:creator>Daniel McDicken</dc:creator>
		<pubDate>Wed, 24 Jun 2009 21:42:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.root777.com/?p=31#comment-1944</guid>
		<description>LoL but funny to watch chrome crash! :P Bug&#039;s in the worx...

PoC Working/Exploit:
Click for a demo (clicking will cause the browser to crash) 
HERE.</description>
		<content:encoded><![CDATA[<p>LoL but funny to watch chrome crash! <img src='http://www.root777.com/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' />  Bug&#8217;s in the worx&#8230;</p>
<p>PoC Working/Exploit:<br />
Click for a demo (clicking will cause the browser to crash)<br />
HERE.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Armen Shirvanian</title>
		<link>http://www.root777.com/security-vulnerability/how-to-crash-google-chrome/comment-page-1/#comment-1843</link>
		<dc:creator>Armen Shirvanian</dc:creator>
		<pubDate>Mon, 01 Dec 2008 07:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.root777.com/?p=31#comment-1843</guid>
		<description>A publicly presented exploit is one that would probably be fixed in a very short period of time.  Google probably saw messages like this either sent to them or written on a site, and then got to work to remove the glitch that could be caused by said hovering.  Finding glitches gets harder and harder over time, as the product is made more error-proof.</description>
		<content:encoded><![CDATA[<p>A publicly presented exploit is one that would probably be fixed in a very short period of time.  Google probably saw messages like this either sent to them or written on a site, and then got to work to remove the glitch that could be caused by said hovering.  Finding glitches gets harder and harder over time, as the product is made more error-proof.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.370 seconds -->
