<?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: Bloglines Withdrawal</title>
	<atom:link href="http://steelwhitetable.org/2006/02/20/bluhglines-withdrawal/feed/" rel="self" type="application/rss+xml" />
	<link>http://steelwhitetable.org/2006/02/20/bluhglines-withdrawal/</link>
	<description>I like maxims that don't encourage behavior modification.</description>
	<pubDate>Sat, 22 Nov 2008 13:01:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Jody</title>
		<link>http://steelwhitetable.org/2006/02/20/bluhglines-withdrawal/#comment-7820</link>
		<dc:creator>Jody</dc:creator>
		<pubDate>Wed, 22 Feb 2006 00:38:37 +0000</pubDate>
		<guid isPermaLink="false">http://steelwhitetable.org/blog/2006/02/20/bloglines-withdrawal/#comment-7820</guid>
		<description>I did some investigation and it appeared our work's servers were infected by something that redirected some IPs.  We informed infrastructure and they confirmed my findings:
&lt;blockquote&gt;&lt;em&gt;Symantec Enterprise Security Gateway products include a DNS proxy, DNSd, which functions as a DNS server. Symantec resolved a DNS cache-poisoning vulnerability that was reported to impact the Symantec Gateway Security products that are listed in the Solution section of this page. Under specific conditions and configurations, incorrect or false DNS records could be inserted into the DNS cache tables, resulting in incorrect responses to legitimate DNS requests.&lt;/em&gt;&lt;/blockquote&gt;
They fixed it today.</description>
		<content:encoded><![CDATA[<p>I did some investigation and it appeared our work&#8217;s servers were infected by something that redirected some IPs.  We informed infrastructure and they confirmed my findings:</p>
<blockquote><p><em>Symantec Enterprise Security Gateway products include a DNS proxy, DNSd, which functions as a DNS server. Symantec resolved a DNS cache-poisoning vulnerability that was reported to impact the Symantec Gateway Security products that are listed in the Solution section of this page. Under specific conditions and configurations, incorrect or false DNS records could be inserted into the DNS cache tables, resulting in incorrect responses to legitimate DNS requests.</em></p></blockquote>
<p>They fixed it today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip</title>
		<link>http://steelwhitetable.org/2006/02/20/bluhglines-withdrawal/#comment-7813</link>
		<dc:creator>Phillip</dc:creator>
		<pubDate>Tue, 21 Feb 2006 14:03:52 +0000</pubDate>
		<guid isPermaLink="false">http://steelwhitetable.org/blog/2006/02/20/bloglines-withdrawal/#comment-7813</guid>
		<description>What a relief.</description>
		<content:encoded><![CDATA[<p>What a relief.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://steelwhitetable.org/2006/02/20/bluhglines-withdrawal/#comment-7811</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 21 Feb 2006 03:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://steelwhitetable.org/blog/2006/02/20/bloglines-withdrawal/#comment-7811</guid>
		<description>Hmmmm....  works from home.</description>
		<content:encoded><![CDATA[<p>Hmmmm&#8230;.  works from home.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jody</title>
		<link>http://steelwhitetable.org/2006/02/20/bluhglines-withdrawal/#comment-7810</link>
		<dc:creator>Jody</dc:creator>
		<pubDate>Mon, 20 Feb 2006 18:22:19 +0000</pubDate>
		<guid isPermaLink="false">http://steelwhitetable.org/blog/2006/02/20/bloglines-withdrawal/#comment-7810</guid>
		<description>Yes, I'm still getting it.  Maybe our workplace is redirecting bloglines' IP.  The bastards.</description>
		<content:encoded><![CDATA[<p>Yes, I&#8217;m still getting it.  Maybe our workplace is redirecting bloglines&#8217; IP.  The bastards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rekounas</title>
		<link>http://steelwhitetable.org/2006/02/20/bluhglines-withdrawal/#comment-7809</link>
		<dc:creator>rekounas</dc:creator>
		<pubDate>Mon, 20 Feb 2006 18:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://steelwhitetable.org/blog/2006/02/20/bloglines-withdrawal/#comment-7809</guid>
		<description>Seems to be up and running now.

Very wierd.  Are you still getting the message Jody?</description>
		<content:encoded><![CDATA[<p>Seems to be up and running now.</p>
<p>Very wierd.  Are you still getting the message Jody?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jody</title>
		<link>http://steelwhitetable.org/2006/02/20/bluhglines-withdrawal/#comment-7808</link>
		<dc:creator>Jody</dc:creator>
		<pubDate>Mon, 20 Feb 2006 17:45:22 +0000</pubDate>
		<guid isPermaLink="false">http://steelwhitetable.org/blog/2006/02/20/bloglines-withdrawal/#comment-7808</guid>
		<description>I'll update the post above with an image from the site, to show I haven't been drinking again.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll update the post above with an image from the site, to show I haven&#8217;t been drinking again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J-Walk</title>
		<link>http://steelwhitetable.org/2006/02/20/bluhglines-withdrawal/#comment-7807</link>
		<dc:creator>J-Walk</dc:creator>
		<pubDate>Mon, 20 Feb 2006 17:42:12 +0000</pubDate>
		<guid isPermaLink="false">http://steelwhitetable.org/blog/2006/02/20/bloglines-withdrawal/#comment-7807</guid>
		<description>That's strange. I haven't noticed any downtime at Bloglines, and everything appears to be working normally. In fact, I found this post via Bloglines.</description>
		<content:encoded><![CDATA[<p>That&#8217;s strange. I haven&#8217;t noticed any downtime at Bloglines, and everything appears to be working normally. In fact, I found this post via Bloglines.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
