<?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: Secure WI-FI Requires New Hardware</title>
	<atom:link href="http://www.forevergeek.com/2004/05/secure_wi_fi_requires_new_hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.forevergeek.com/2004/05/secure_wi_fi_requires_new_hardware/</link>
	<description>Nerds are for Dorks</description>
	<lastBuildDate>Sat, 21 Nov 2009 10:14:48 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: JC</title>
		<link>http://www.forevergeek.com/2004/05/secure_wi_fi_requires_new_hardware/comment-page-1/#comment-1274</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Tue, 11 May 2004 15:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://forevergeek.com/?p=332#comment-1274</guid>
		<description>no, SSL *and* VPN. I was talking about secure websites, but obviously VPN traffic is also important.
And yeah... sorry, I thought I was conveying that when I said &quot;it&#039;s still going in cleartext all the way from the router to the server&quot; but I see that wasn&#039;t very clear. But the bit before the router isn&#039;t as important on a wired network.

Well, I suppose it could be if someone had popped one of &lt;a href=&quot;http://www.dcphonehome.com/&quot; rel=&quot;nofollow&quot;&gt;these&lt;/a&gt; (via &lt;a href=&quot;http://www.wired.com/news/culture/0,1284,54328,00.html&quot; rel=&quot;nofollow&quot;&gt;Wired&lt;/a&gt;) in an out of the way place in your network. But someone would have to have physical access, and at that point you&#039;re screwed anyway, no matter what. 
</description>
		<content:encoded><![CDATA[<p>no, SSL *and* VPN. I was talking about secure websites, but obviously VPN traffic is also important.<br />
And yeah&#8230; sorry, I thought I was conveying that when I said &#8220;it&#8217;s still going in cleartext all the way from the router to the server&#8221; but I see that wasn&#8217;t very clear. But the bit before the router isn&#8217;t as important on a wired network.</p>
<p>Well, I suppose it could be if someone had popped one of <a href="http://www.dcphonehome.com/" rel="nofollow">these</a> (via <a href="http://www.wired.com/news/culture/0,1284,54328,00.html" rel="nofollow">Wired</a>) in an out of the way place in your network. But someone would have to have physical access, and at that point you&#8217;re screwed anyway, no matter what.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janne</title>
		<link>http://www.forevergeek.com/2004/05/secure_wi_fi_requires_new_hardware/comment-page-1/#comment-1273</link>
		<dc:creator>Janne</dc:creator>
		<pubDate>Tue, 11 May 2004 12:58:09 +0000</pubDate>
		<guid isPermaLink="false">http://forevergeek.com/?p=332#comment-1273</guid>
		<description>No, no SSL.

VPN.

Use the CPU of the laptop to do the encryption, and you&#039;re fine. I think it&#039;s a nice balance anyway: keeps the chipsets cheap, and finds use for the massive CPU power you bought to run Word. :)

And your emails travel unencrypted in the wired internet, too.</description>
		<content:encoded><![CDATA[<p>No, no SSL.</p>
<p>VPN.</p>
<p>Use the CPU of the laptop to do the encryption, and you&#8217;re fine. I think it&#8217;s a nice balance anyway: keeps the chipsets cheap, and finds use for the massive CPU power you bought to run Word. :)</p>
<p>And your emails travel unencrypted in the wired internet, too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JC</title>
		<link>http://www.forevergeek.com/2004/05/secure_wi_fi_requires_new_hardware/comment-page-1/#comment-1272</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Mon, 10 May 2004 13:29:18 +0000</pubDate>
		<guid isPermaLink="false">http://forevergeek.com/?p=332#comment-1272</guid>
		<description>Well, the people who really want the stronger security (outside of a few paranoids) are the corporate IT people, and they have the pockets for the more expensive hardware. Anything really sensitive on the web is going to be encrypted via SSL anyway... it&#039;s email that&#039;s the real headache... you can use SSL for your username and password if the server supports it... but the email&#039;s still sent in the clear unless you use pgp or something, and that&#039;s a headache most people don&#039;t want to deal with in every email, just in the really sensitive ones... and of course, a stronger wifi encryption standard won&#039;t change that very much, since it&#039;s still going in cleartext all the way from the router to the server.

On the other hand, when I&#039;m running a little linux install using &lt;a href=&quot;http://h.vu.wifi-box.net/&quot; rel=&quot;nofollow&quot;&gt;custom&lt;/a&gt; &lt;a href=&quot;http://docs.sveasoft.com/SV-Guide.html&quot; rel=&quot;nofollow&quot;&gt;firmware&lt;/a&gt; on my linksys 802.11g router... have to wonder what will be possible when more processing power is introduced.</description>
		<content:encoded><![CDATA[<p>Well, the people who really want the stronger security (outside of a few paranoids) are the corporate IT people, and they have the pockets for the more expensive hardware. Anything really sensitive on the web is going to be encrypted via SSL anyway&#8230; it&#8217;s email that&#8217;s the real headache&#8230; you can use SSL for your username and password if the server supports it&#8230; but the email&#8217;s still sent in the clear unless you use pgp or something, and that&#8217;s a headache most people don&#8217;t want to deal with in every email, just in the really sensitive ones&#8230; and of course, a stronger wifi encryption standard won&#8217;t change that very much, since it&#8217;s still going in cleartext all the way from the router to the server.</p>
<p>On the other hand, when I&#8217;m running a little linux install using <a href="http://h.vu.wifi-box.net/" rel="nofollow">custom</a> <a href="http://docs.sveasoft.com/SV-Guide.html" rel="nofollow">firmware</a> on my linksys 802.11g router&#8230; have to wonder what will be possible when more processing power is introduced.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janne</title>
		<link>http://www.forevergeek.com/2004/05/secure_wi_fi_requires_new_hardware/comment-page-1/#comment-1271</link>
		<dc:creator>Janne</dc:creator>
		<pubDate>Mon, 10 May 2004 11:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://forevergeek.com/?p=332#comment-1271</guid>
		<description>It was. Unfortunately, the algorithm was chosen on the principle that they could be implemented cheaply with simple hardware and few gates.

Which means that it was weak from the beginning.  But it did help WiFi to become more pervasive by allowing really cheap hardware.  So whether it was a good or a bad thing is hard to say.</description>
		<content:encoded><![CDATA[<p>It was. Unfortunately, the algorithm was chosen on the principle that they could be implemented cheaply with simple hardware and few gates.</p>
<p>Which means that it was weak from the beginning.  But it did help WiFi to become more pervasive by allowing really cheap hardware.  So whether it was a good or a bad thing is hard to say.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
