<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Vulnerable NetDDE Shares Lead To Complete System Compromise</title>
	<atom:link href="http://www.digitalbond.com/index.php/2008/01/29/vulnerable-netdde-shares-lead-to-complete-system-compromise/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalbond.com/index.php/2008/01/29/vulnerable-netdde-shares-lead-to-complete-system-compromise/</link>
	<description>This Month in Control System Security</description>
	<lastBuildDate>Thu, 09 Sep 2010 20:36:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: OPC Exchange Blog, Featuring Eric Murphy &#187; Blog Archive &#187; netDDE-EEK!</title>
		<link>http://www.digitalbond.com/index.php/2008/01/29/vulnerable-netdde-shares-lead-to-complete-system-compromise/comment-page-1/#comment-9245</link>
		<dc:creator>OPC Exchange Blog, Featuring Eric Murphy &#187; Blog Archive &#187; netDDE-EEK!</dc:creator>
		<pubDate>Fri, 01 Feb 2008 05:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalbond.com/index.php/2008/01/29/vulnerable-netdde-shares-lead-to-complete-system-compromise/#comment-9245</guid>
		<description>[...] Digital Bond blog has more details on the netDDE Share vulnerability announced by US CERT.    It’s not really shocking news that netDDE is lacking in the security [...]</description>
		<content:encoded><![CDATA[<p>[...] Digital Bond blog has more details on the netDDE Share vulnerability announced by US CERT.    It’s not really shocking news that netDDE is lacking in the security [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
