<?xml version="1.0"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Switched - Comments for Google's Chrome Browser Vulnerable to Hackers</title>
<link>http://www.switched.com/2008/09/03/googles-chrome-browser-vulnerable-to-hackers/</link>
<description>Switched Comments for Google's Chrome Browser Vulnerable to Hackers</description>
<image>
<url>http://www.switched.com/media/feedlogo.gif</url>
<title>Switched</title>
<link>http://www.switched.com</link>
</image>
<language>en-us</language>
<copyright>Copyright 2012 Weblogs, Inc. The contents of this feed are available for non-commercial use only.</copyright>
<generator>Blogsmith http://www.blogsmith.com/</generator><item><title><![CDATA[Comments on Google's Chrome Browser Vulnerable to Hackers]]></title><link>http://www.switched.com/2008/09/03/googles-chrome-browser-vulnerable-to-hackers/</link><guid isPermaLink="true">http://www.switched.com/2008/09/03/googles-chrome-browser-vulnerable-to-hackers/</guid><description><![CDATA[If I remember correctly, that Safari issue was significantly more deadly than the one you describe for Chrome. The Safari issue would not only download the file, but execute it without your knowledge.<br><br>Also, I think the flaw is actually with *webkit*, not with Chrome. Of course, it's Google's fault that they haven't implemented the latest version, but I think it's entirely reasonable that they will do so pretty soon.]]></description><dc:creator><![CDATA[jay.kopper]]></dc:creator><pubDate>Sep 3rd 2008 12:31PM</pubDate></item></channel></rss>
