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

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Wireless networking needs to grow up in Wireless Security</title>
<link>http://www.dslreports.com/forum/r20951182</link>
<description></description>
<language>en</language>
<pubDate>Tue, 15 Dec 2009 02:52:35 EDT</pubDate>
<lastBuildDate>Tue, 15 Dec 2009 02:52:35 EDT</lastBuildDate>

<item>
<title>Re: Wireless networking needs to grow up</title>
<link>http://www.dslreports.com/forum/remark,20951679</link>
<description><![CDATA[<A HREF="/useremail/u/772729"><b>Nerdtalker</b></A> : Why would it reset itself to defaults? <br><br>This is a vendor specific hardware/firmware issue and not really something systemically wrong with WiFi itself. I agree with you and Steve/Leo that a vast majority of SOHO wifi routers are complete crap. From top to bottom, the firmware, the software, the web configuration tools. All crap. <br><br>That said, you <i>can</i> get good near-enterprise level stability with something like a WRT54GL/GLS/G/TM running Tomato; complete with the HTTPS: web management pages.<br><br>If people aren't willing to spend the money to get decent hardware, and vendors really don't care about firmware that doesn't lock up when you enable WPA/WPA2, then stuff like this is gonna happen. <br><br>That said, it isn't like wireless networking really needs to grow up. WPA2 with RADIUS/EAP/PEAP and certificates is bulletproof. Period; the problem is that on a consumer-level this isn't practical at all.<br><small>--<br>"Some people never see the light till it shines thru bullet holes." -Bruce Cockburn<br><br>I'm testing Gmail's spam filters: Broadbandreports1@gmail.com<br><b>Spam: 12900+</b> messages currently using 406 MB.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20951679</guid>
<pubDate>Thu, 14 Aug 2008 17:16:22 EDT</pubDate>
</item>

<item>
<title>Re: Wireless networking needs to grow up</title>
<link>http://www.dslreports.com/forum/remark,20951308</link>
<description><![CDATA[<A HREF="/useremail/u/1357530"><b>Bink</b></A> : Stop spreading drivel.  There is no wireless security flaw here&#151;and if there is, it&#146;s related to insufficient network management/maintenance and clueless vendors that continue to ship their products insecure by default.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20951308</guid>
<pubDate>Thu, 14 Aug 2008 16:05:23 EDT</pubDate>
</item>

<item>
<title>Wireless networking needs to grow up</title>
<link>http://www.dslreports.com/forum/remark,20951182</link>
<description><![CDATA[<A HREF="/useremail/u/595148"><b>aefstoggaflm</b></A> : Another new wireless security flaw.  :uhh:<br><br>As addressed in <A HREF="http://www.grc.com/sn/sn-152.htm">Security Now! with Steve Gibson, Episode 152 for July 10, 2008: Listener Feedback #45</a><br><br> <blockquote><small>quote:</small><hr>Leo: Yeah. Thanks, airport. They would go through the airport screening area and continue on with their life, not knowing they connected to our network. That would also explain why none of the devices were live when I tried to locate them. The problem with the WAP turned out to be that it had reset itself back to factory defaults. I didn't want to have to climb up in the ceiling to replace the WAP, so I quickly reconfigured it back to its formerly secure state. Upon restarting the WAP, it was back to default settings again.<br><hr></blockquote><br><small>--<br>Please use the "yellow (IM) envelope" to contact me and please leave the URL intact.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20951182</guid>
<pubDate>Thu, 14 Aug 2008 15:40:31 EDT</pubDate>
</item>

</channel>
</rss>
