<?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/"
		>
<channel>
	<title>Comments for Suncoast Security Society : Security Corner</title>
	<atom:link href="http://suncoastsecuritysociety.org/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://suncoastsecuritysociety.org/blog</link>
	<description>Security Musings from the Grid</description>
	<lastBuildDate>Thu, 13 Aug 2009 01:49:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Querying and identifying PCI devices by shartman</title>
		<link>http://suncoastsecuritysociety.org/blog/2009/06/05/querying-and-identifying-pci-devices/comment-page-1/#comment-889</link>
		<dc:creator>shartman</dc:creator>
		<pubDate>Thu, 13 Aug 2009 01:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://suncoastsecuritysociety.org/blog/2009/06/05/querying-and-identifying-pci-devices/#comment-889</guid>
		<description>Thanks for the comment. I pulled the information from Microsoft&#039;s MSDN site on how to identify devices. Do you know if there is a universal list or another way to programmically identify wireless devices vs. standard ethernet controllers.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment. I pulled the information from Microsoft&#8217;s MSDN site on how to identify devices. Do you know if there is a universal list or another way to programmically identify wireless devices vs. standard ethernet controllers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Querying and identifying PCI devices by Suede Worthey</title>
		<link>http://suncoastsecuritysociety.org/blog/2009/06/05/querying-and-identifying-pci-devices/comment-page-1/#comment-888</link>
		<dc:creator>Suede Worthey</dc:creator>
		<pubDate>Thu, 13 Aug 2009 01:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://suncoastsecuritysociety.org/blog/2009/06/05/querying-and-identifying-pci-devices/#comment-888</guid>
		<description>Your assumption about the device IDs of wireless devices beginning with 4 is inaccurate. This is true for some Wireless adapters, but definitely not all. There are many wireless adapters based on the Atheros chipset, and many of their device IDs begin with 0. Not to mention, there could be some other NICs from the same vendor whose device IDs begin with 4 and are not wireless.
Thanks,
Suede</description>
		<content:encoded><![CDATA[<p>Your assumption about the device IDs of wireless devices beginning with 4 is inaccurate. This is true for some Wireless adapters, but definitely not all. There are many wireless adapters based on the Atheros chipset, and many of their device IDs begin with 0. Not to mention, there could be some other NICs from the same vendor whose device IDs begin with 4 and are not wireless.<br />
Thanks,<br />
Suede</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is Perl and how do I get started by Sarah</title>
		<link>http://suncoastsecuritysociety.org/blog/2009/06/18/what-is-perl-and-how-do-i-get-started/comment-page-1/#comment-878</link>
		<dc:creator>Sarah</dc:creator>
		<pubDate>Wed, 24 Jun 2009 02:07:25 +0000</pubDate>
		<guid isPermaLink="false">http://suncoastsecuritysociety.org/blog/2009/06/18/what-is-perl-and-how-do-i-get-started/#comment-878</guid>
		<description>Pretty good post. I just came by your blog and wanted to say 
that I&#039;ve really liked reading your blog posts. In any case 
I&#039;ll be subscribing to your feed and I hope you write again soon!</description>
		<content:encoded><![CDATA[<p>Pretty good post. I just came by your blog and wanted to say<br />
that I&#8217;ve really liked reading your blog posts. In any case<br />
I&#8217;ll be subscribing to your feed and I hope you write again soon!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
