<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Speeding NEO's Weblog</title>
	<atom:link href="http://speedinneo.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://speedinneo.wordpress.com</link>
	<description>It's All About Poop!</description>
	<lastBuildDate>Wed, 30 Apr 2008 05:53:48 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Kodak&#8217;s Image Viewer Is Broken &#8211; Microsoft&#8217;s Answer To The Problem by msoftsucks</title>
		<link>http://speedinneo.wordpress.com/2007/11/09/kodaks-image-viewer-is-broken-microsofts-answer-to-the-problem/#comment-27</link>
		<dc:creator>msoftsucks</dc:creator>
		<pubDate>Wed, 30 Apr 2008 05:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://speedinneo.wordpress.com/2007/11/09/kodaks-image-viewer-is-broken-microsofts-answer-to-the-problem/#comment-27</guid>
		<description>Great piece!  I fell asleep at the switch and naively downloaded the patch that was supposed to take care of the remote code execution problem of Kodak&#039;s Image Viewer and am now getting the damn pop-up warning.  Any ideas of how to get stop the annoying pop-up, or better yet, uninsall the patch?</description>
		<content:encoded><![CDATA[<p>Great piece!  I fell asleep at the switch and naively downloaded the patch that was supposed to take care of the remote code execution problem of Kodak&#8217;s Image Viewer and am now getting the damn pop-up warning.  Any ideas of how to get stop the annoying pop-up, or better yet, uninsall the patch?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Free Security Holes For Your Computer by belucid</title>
		<link>http://speedinneo.wordpress.com/2007/11/03/free-security-holes-for-your-computer/#comment-23</link>
		<dc:creator>belucid</dc:creator>
		<pubDate>Wed, 07 Nov 2007 21:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://speedinneo.wordpress.com/2007/11/03/free-security-holes-for-your-computer/#comment-23</guid>
		<description>I&#039;m very glad you brought this topic up as it has caused me to reconsider this issue. OminFind Yahoo! Edition is meant to be used on a server not a desktop so I tend to assume one of two things. I assume either the server in question is a web server so you actually intend for OmniFind Yahoo! Edition search to be exposed to the Internet because you are using it for site search, far from being a security hole, you want to expose your search to your customers or partners. Or I assume the server in question is a departmental or workgroup server serving a community of a few to a few thousand internal users behind a firewall and of course no one is browsing the Internet from the server so browser vulnerabilities like Java or ActiveX access to localhost are not an issue. It is of course the case that people do deploy OmniFind Yahoo! Edition on their desktops for testing, evaluation or development (hopefully not for desktop search, consider the other alternatives that are targeted at this use) so we can&#039;t simply ignore the point you have brought up. I have added an FAQ to the OminFind Yahoo! Edition forums to cover this topic: 

http://omnifind.ibm.yahoo.net/forums/index.php/topic,958.0.html

Again, thanks for raising this issue.

Regards,
Sean
(IBM OmniFind Yahoo! Edition Product Manager)</description>
		<content:encoded><![CDATA[<p>I&#8217;m very glad you brought this topic up as it has caused me to reconsider this issue. OminFind Yahoo! Edition is meant to be used on a server not a desktop so I tend to assume one of two things. I assume either the server in question is a web server so you actually intend for OmniFind Yahoo! Edition search to be exposed to the Internet because you are using it for site search, far from being a security hole, you want to expose your search to your customers or partners. Or I assume the server in question is a departmental or workgroup server serving a community of a few to a few thousand internal users behind a firewall and of course no one is browsing the Internet from the server so browser vulnerabilities like Java or ActiveX access to localhost are not an issue. It is of course the case that people do deploy OmniFind Yahoo! Edition on their desktops for testing, evaluation or development (hopefully not for desktop search, consider the other alternatives that are targeted at this use) so we can&#8217;t simply ignore the point you have brought up. I have added an FAQ to the OminFind Yahoo! Edition forums to cover this topic: </p>
<p><a href="http://omnifind.ibm.yahoo.net/forums/index.php/topic,958.0.html" rel="nofollow">http://omnifind.ibm.yahoo.net/forums/index.php/topic,958.0.html</a></p>
<p>Again, thanks for raising this issue.</p>
<p>Regards,<br />
Sean<br />
(IBM OmniFind Yahoo! Edition Product Manager)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Free Security Holes For Your Computer by speedinneo</title>
		<link>http://speedinneo.wordpress.com/2007/11/03/free-security-holes-for-your-computer/#comment-21</link>
		<dc:creator>speedinneo</dc:creator>
		<pubDate>Mon, 05 Nov 2007 23:36:14 +0000</pubDate>
		<guid isPermaLink="false">http://speedinneo.wordpress.com/2007/11/03/free-security-holes-for-your-computer/#comment-21</guid>
		<description>One comment is posted, and placed on the November 5th entry, &quot;Local Search Engines - Potential Security Holes - Is It True?&quot;</description>
		<content:encoded><![CDATA[<p>One comment is posted, and placed on the November 5th entry, &#8220;Local Search Engines &#8211; Potential Security Holes &#8211; Is It True?&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
