<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns="http://purl.org/rss/1.0/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
>

  <channel rdf:about="http://lwn.net/headlines/191100/">
    <title>LWN: Comments on "Wireless networking driver vulnerabilities"</title>
    <link>http://lwn.net/Articles/191100/</link>
    <description>
This is a special feed containing comments posted
to the individual LWN article titled &quot;Wireless networking driver vulnerabilities&quot;.

    </description>

    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>2</syn:updateFrequency>
    <items>
      <rdf:Seq>
	<rdf:li resource="http://lwn.net/Articles/191351/rss" />
	<rdf:li resource="http://lwn.net/Articles/191254/rss" />
	<rdf:li resource="http://lwn.net/Articles/191221/rss" />
	<rdf:li resource="http://lwn.net/Articles/191215/rss" />
      
      </rdf:Seq>
    </items>

  </channel>
    <item rdf:about="http://lwn.net/Articles/191351/rss">
      <title>Wireless networking driver vulnerabilities</title>
      <link>http://lwn.net/Articles/191351/rss</link>
      <dc:date>2006-07-14T08:38:35+00:00</dc:date>
      <dc:creator>eskild</dc:creator>
      <description>
      Hahaha, didn't catch that when I wrote it  8-)  Thanks, your comment made me laugh.&lt;br&gt;
&lt;p&gt;
Re. Cobol: I think someone once said something along the lines of: &quot;The mistakes we make will come back to haunt us, indefinitely.&quot; Well, maybe not indefinitely, but for a long while; decades. It's funny how we always underestimate how long our systems remain in production use. Technology is very uneven that way: Some (albeit few) people still run on VAX machines today, but we sometimes worry that we won't be able to read our digital content 10 years from now because of newer formats replacing the old. It's very hard to predict what has longevity and what hasn't.&lt;br&gt;
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/191254/rss">
      <title>Wireless networking driver vulnerabilities</title>
      <link>http://lwn.net/Articles/191254/rss</link>
      <dc:date>2006-07-13T17:12:47+00:00</dc:date>
      <dc:creator>smitty_one_each</dc:creator>
      <description>
      From TFA:&lt;br&gt;
&lt;font class=&quot;QuotedText&quot;&gt;&amp;gt;They also examined other networking technologies including Bluetooth, Ev-Do (EVolution-Data Only), and HSDPA (High Speed Downlink Packet Access). &lt;/font&gt;&lt;br&gt;
&lt;p&gt;
The article wasn't clear whether or not the attacks used were staged against encrypted 802.11g networks.&lt;br&gt;
&lt;p&gt;
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/191221/rss">
      <title>Wireless networking driver vulnerabilities</title>
      <link>http://lwn.net/Articles/191221/rss</link>
      <dc:date>2006-07-13T14:45:04+00:00</dc:date>
      <dc:creator>mmarsh</dc:creator>
      <description>
      &lt;pre&gt;
&gt; That's a huge windows of vulnerability.
                ^^^^^^^
&lt;/pre&gt;
&lt;p&gt;
Freudian slip?
&lt;/p&gt;
&lt;p&gt;
I actually heard an add on the radio recently for a company looking to hire Cobol programmers.
&lt;/p&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/191215/rss">
      <title>Wireless networking driver vulnerabilities</title>
      <link>http://lwn.net/Articles/191215/rss</link>
      <dc:date>2006-07-13T14:08:36+00:00</dc:date>
      <dc:creator>eskild</dc:creator>
      <description>
      I think some of the reasons why securty lessons don't seem fully applied to new designs are:&lt;br&gt;
&lt;p&gt;
* It is really, really hard to do a good, secure design&lt;br&gt;
* It thus takes a lot of time and effort to do&lt;br&gt;
* But customers want &quot;feature X&quot; NOW, NOW, NOW, or that's at least what everybody seems to think&lt;br&gt;
&lt;p&gt;
Who wins? Money wins: Provide a product ASAP, even if security is mediocre, and sell tons of units. Sad part is that the customers are the ones to suffer at the end.&lt;br&gt;
&lt;p&gt;
Another observation is this: If a product/design with lousy security gets &quot;first-mover&quot; advantage in a market and sales booms, then it may live for years, perhaps decades, before being replaced with something better. That's a huge windows of vulnerability. Think Telnet, FTP, and any clear-text protocol you may care to mention. They're still with us, even though they should have been put to rest years ago. Think wireless WEP security -- &quot;wired equivalent&quot; security, anyone?! OMG! (On a sadistic note, think Fortran, think Cobol! (OK, Only kidding! ;-))&lt;br&gt;
&lt;p&gt;
Enough ranting. Thanks for reading.&lt;br&gt;
      
      </description>
    </item>
</rdf:RDF>

