<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:fe="http://tommorris.org/ns/fireeagle/" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:georss="http://www.georss.org/georss" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
  <channel><title>Tom Morris</title><link>http://tommorris.org/blog/</link><description>The latest posts from my blog.</description>
<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/TomMorrisOPML" type="application/rss+xml" /><feedburner:emailServiceId>TomMorrisOPML</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item><title>Why Pre-Shared Keys Suck</title><description>&lt;p&gt;1. Guest comes to Owner's place and asks for wifi key.&lt;/p&gt;
    &lt;p&gt;2. Owner tells Guest that the password is "flibble".&lt;/p&gt;
    &lt;p&gt;3. Guest logs on.&lt;/p&gt;
    &lt;p&gt;4. Guest leaves and tells the world that Owner's wifi key is "flibble".&lt;/p&gt;
    &lt;p&gt;5. Owner must now change his wifi key from "flibble" to something else and then inform everybody else who uses the wifi (both humans and devices which store the pre-shared key) what the new key is.&lt;/p&gt;
    &lt;p&gt;6. Goto (1)&lt;/p&gt;
    &lt;p&gt;The alternative to pre-shared key systems is to have a user account system.&lt;/p&gt;
    &lt;p&gt;1. Guest comes to Owner's place and asks for wifi key.&lt;/p&gt;
    &lt;p&gt;2. Owner logs onto administration panel, taps in username and generates a password, then gives that to Guest.&lt;/p&gt;
    &lt;p&gt;3. Guest uses.&lt;/p&gt;
    &lt;p&gt;4. If Guest tells the world his wifi username and password combo, you revoke the password.&lt;/p&gt;
    &lt;p&gt;There is no reason why this setup should not be used in consumer wifi routers, except for the fact that the existing standards for wifi authentication are designed for mouth-breathing idiots who share their fucking MySpace passwords with each other and then wonder why their account gets "hacked".&lt;/p&gt;
    &lt;p&gt;And before anyone says &lt;a href= "http://freeradius.org/"&gt;FreeRADIUS&lt;/a&gt;, that's too complex. Yes, I can set up FreeRADIUS on my Linux box. But username/password authentication &lt;em&gt;with&lt;/em&gt; integration at the OS level with Windows and UNIX (including OS X and Linux) should ship on consumer-level wifi routers. That wouldn't suck. Pre-shared keys do suck and are actually worse than useless.&lt;/p&gt;
    &lt;p&gt;Another thing I don't understand about wifi: why is it that the only way to get encryption of your packets across the air is to turn on authentication? Sometimes I want unauthenticated wifi but that doesn't mean I don't want my packets encrypted. Think of it like a club: just because there's no guest list doesn't mean that you don't need security. In fact, you probably need &lt;em&gt;more&lt;/em&gt; security.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/TomMorrisOPML/~4/zq4eLSbNbfk" height="1" width="1"/&gt;</description><pubDate>Wed, 01 Jul 2009 20:45:50 GMT</pubDate><link>http://tommorris.org/blog/2009/07/01#When:20:45:50</link><guid isPermaLink="false">http://tommorris.org/blog/2009/07/01#When:20:45:50</guid></item></channel>
</rss>
