<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Google Desktop security flaw is fixed</title>
	<atom:link href="http://blogs.law.harvard.edu/jkbaumga/2007/02/21/google-desktop-security-flaw-is-fixed/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/jkbaumga/2007/02/21/google-desktop-security-flaw-is-fixed/</link>
	<description>December already~</description>
	<lastBuildDate>Tue, 10 Nov 2009 19:02:36 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: sheds</title>
		<link>http://blogs.law.harvard.edu/jkbaumga/2007/02/21/google-desktop-security-flaw-is-fixed/comment-page-1/#comment-5695</link>
		<dc:creator>sheds</dc:creator>
		<pubDate>Sat, 23 Jun 2007 06:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/jkbaumga/2007/02/21/google-desktop-security-flaw-is-fixe#comment-5695</guid>
		<description>It&#039;s reassuring to know they fixed it eventually........

Mark (&lt;a href=&quot;http://www.buyashed.com.au&quot; rel=&quot;nofollow&quot;&gt;sheds&lt;/a&gt;)</description>
		<content:encoded><![CDATA[<p>It&#8217;s reassuring to know they fixed it eventually&#8230;&#8230;..</p>
<p>Mark (<a href="http://www.buyashed.com.au" rel="nofollow">sheds</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://blogs.law.harvard.edu/jkbaumga/2007/02/21/google-desktop-security-flaw-is-fixed/comment-page-1/#comment-3650</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Wed, 21 Feb 2007 17:08:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/jkbaumga/2007/02/21/google-desktop-security-flaw-is-fixe#comment-3650</guid>
		<description>Hi Chris

Watchfire Corp has a whitepaper out on the Google Desktop security flaw

http://download.watchfire.com/whitepapers/Overtaking-Google-Desktop.pdf

Hope this is helpful</description>
		<content:encoded><![CDATA[<p>Hi Chris</p>
<p>Watchfire Corp has a whitepaper out on the Google Desktop security flaw</p>
<p><a href="http://download.watchfire.com/whitepapers/Overtaking-Google-Desktop.pdf" rel="nofollow">http://download.watchfire.com/whitepapers/Overtaking-Google-Desktop.pdf</a></p>
<p>Hope this is helpful</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blogs.law.harvard.edu/jkbaumga/2007/02/21/google-desktop-security-flaw-is-fixed/comment-page-1/#comment-3649</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 21 Feb 2007 16:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/jkbaumga/2007/02/21/google-desktop-security-flaw-is-fixe#comment-3649</guid>
		<description>That&#039;s a little odd.  The article talks about cross-site scripting attacks as if they&#039;re equivalent to viruses, whereas they&#039;re usually the weakest and least dangerous form of exploit.  Maybe this one&#039;s different somehow?  I wonder how it goes from cross-site scripting to full control of the owner&#039;s machine..

- Chris.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a little odd.  The article talks about cross-site scripting attacks as if they&#8217;re equivalent to viruses, whereas they&#8217;re usually the weakest and least dangerous form of exploit.  Maybe this one&#8217;s different somehow?  I wonder how it goes from cross-site scripting to full control of the owner&#8217;s machine..</p>
<p>- Chris.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
