<?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 on: Wireless Driver Vulnerabilities</title>
	<atom:link href="http://www.averyjparker.com/2006/08/02/wireless-driver-vulnerabilities/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.averyjparker.com/2006/08/02/wireless-driver-vulnerabilities/</link>
	<description>and Internet Security, Windows, Linux, Mac and other Tech Info from Avery J. Parker</description>
	<lastBuildDate>Mon, 07 Feb 2011 05:00:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Mac Wireless driver Security vulnerability revisited-- Avery J. Parker - Web site hosting and computer service</title>
		<link>http://www.averyjparker.com/2006/08/02/wireless-driver-vulnerabilities/comment-page-1/#comment-4621</link>
		<dc:creator>Mac Wireless driver Security vulnerability revisited-- Avery J. Parker - Web site hosting and computer service</dc:creator>
		<pubDate>Sat, 19 Aug 2006 00:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.averyjparker.com/2006/08/02/wireless-driver-vulnerabilities/#comment-4621</guid>
		<description>[...] A couple weeks ago the hot story was about the demonstration of a vulnerability in a 3rd party wireless card driver on a Mac. The individuals that demonstrated the vulnerability (in a video taped presentation) also claimed that many wireless drivers were vulnerable to this same flaw and it included the MacBook native drivers (among others.) There was immediate controversy over the fact it was a video demo. I thought their explanation for that was reasonable. (They didn&#8217;t want to give a room full of crackers a chance to sniff the wireless traffic and get TOO much detail on the exploit before vendors had a good chance to give updates.) Well&#8230; at this point it sounds like among other things, they have not yet demonstrated to Apple an effective use of this exploit against the wireless drivers on the macbook. [...]</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
<!--INFOLINKS_ON--></p>
<p>[...] A couple weeks ago the hot story was about the demonstration of a vulnerability in a 3rd party wireless card driver on a Mac. The individuals that demonstrated the vulnerability (in a video taped presentation) also claimed that many wireless drivers were vulnerable to this same flaw and it included the MacBook native drivers (among others.) There was immediate controversy over the fact it was a video demo. I thought their explanation for that was reasonable. (They didn&#8217;t want to give a room full of crackers a chance to sniff the wireless traffic and get TOO much detail on the exploit before vendors had a good chance to give updates.) Well&#8230; at this point it sounds like among other things, they have not yet demonstrated to Apple an effective use of this exploit against the wireless drivers on the macbook. [...]<br />
<!--INFOLINKS_OFF--><br />
<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
</channel>
</rss>

