<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Michael Gracie &#187; wireless access point</title>
	<atom:link href="http://michaelgracie.com/tag/wireless-access-point/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelgracie.com</link>
	<description>Clever Tagline Unavailable At Publication Time</description>
	<pubDate>Thu, 20 Nov 2008 23:14:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
	<language>en</language>
			<item>
		<title>Why Bruce Schneier Having An Open Wi-Fi Network Is No Good Reason For You To</title>
		<link>http://michaelgracie.com/2008/01/10/why-bruce-schneier-having-an-open-wi-fi-network-is-no-good-reason-for-you-to/</link>
		<comments>http://michaelgracie.com/2008/01/10/why-bruce-schneier-having-an-open-wi-fi-network-is-no-good-reason-for-you-to/#comments</comments>
		<pubDate>Thu, 10 Jan 2008 20:29:48 +0000</pubDate>
		<dc:creator>Michael Gracie</dc:creator>
		
		<category><![CDATA[Office]]></category>

		<category><![CDATA[Bruce Schneier]]></category>

		<category><![CDATA[passwords]]></category>

		<category><![CDATA[security]]></category>

		<category><![CDATA[Tim Lee]]></category>

		<category><![CDATA[wireless]]></category>

		<category><![CDATA[wireless access point]]></category>

		<guid isPermaLink="false">http://michaelgracie.com/2008/01/10/why-bruce-schneier-having-an-open-wi-fi-network-is-no-good-reason-for-you-to/</guid>
		<description><![CDATA[Bruce Schneier, cryptography king, keeps his home network open.  And despite what Tim Lee wrote in support of the idea, please don&#8217;t listen.
The justification is that the risk of someone using your network for illegal means is very low, while the risk of you getting hacked at the local coffee shop is potentially higher. [...]]]></description>
			<content:encoded><![CDATA[<!-- sphereit start --><p>Bruce Schneier, cryptography king, <a href="http://www.wired.com/politics/security/commentary/securitymatters/2008/01/securitymatters_0110">keeps his home network open</a>.  And despite what <a href="http://techdirt.com/articles/20080110/100007.shtml">Tim Lee wrote in support of the idea</a>, please don&#8217;t listen.</p>
<p>The justification is that the risk of someone using your network for illegal means is very low, while the risk of you getting hacked at the local coffee shop is potentially higher.  Hence, worry about your machine, not your home connection.</p>
<p>I say BLAH!  This piss poor argument ignores two significant points:</p>
<p><strong>1) There is little or no benefit to you from opening your network;</strong> and</p>
<p><strong>2) It takes minimal effort to secure your network with a password.</strong></p>
<p>The risks may be low, but meanwhile you have nothing to gain.  Meanwhile, the effort necessary to provide that little extra layer of protection likely outweighs the cost of that single long tail incident - one that could potential cause you tons of legal hassles.</p>
<p>If you are hell bent on providing web access to home visitors, I&#8217;ll take for granted that you trust them.  Give them the key, like I do.  Or if you&#8217;re wearing a tinfoil hat as you hand them their coffee, ask them to allow you to type it in yourself.</p>
<p>UPDATE: Being open can cause hassles (unless you don&#8217;t consider <a href="http://www.boingboing.net/2008/02/06/funny-story-about-co.html">having your computer confiscated by less than technology savvy law enforcement officers</a> a hassle).</p>
<!-- sphereit end -->]]></content:encoded>
			<wfw:commentRss>http://michaelgracie.com/2008/01/10/why-bruce-schneier-having-an-open-wi-fi-network-is-no-good-reason-for-you-to/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Fortune Contributor &#8220;Victim&#8221; of WiFi Hack?</title>
		<link>http://michaelgracie.com/2005/04/15/fortune-contributor-victim-of-wifi-hack/</link>
		<comments>http://michaelgracie.com/2005/04/15/fortune-contributor-victim-of-wifi-hack/#comments</comments>
		<pubDate>Fri, 15 Apr 2005 19:25:27 +0000</pubDate>
		<dc:creator>Michael Gracie</dc:creator>
		
		<category><![CDATA[Spamroll]]></category>

		<category><![CDATA[David Kirkpatrick]]></category>

		<category><![CDATA[Fortune]]></category>

		<category><![CDATA[wireless access point]]></category>

		<category><![CDATA[word]]></category>

		<guid isPermaLink="false">http://www.michaelgracie.com/fortune-contributor-victim-of-wifi-hack/</guid>
		<description><![CDATA[Or simple foolishness.
I read this article from David Kirkpatrick over at FORTUNE, and got to thinking.  What the heck is wrong with this scenario?  Then it hit me.
If you keep your double super-dooper secret passwords in a Word document, on an shared access or otherwise unprotected part of your hard drive, you are [...]]]></description>
			<content:encoded><![CDATA[<!-- sphereit start --><p>Or simple foolishness.</p>
<p>I read <a title="David Kirkpatrick - Identity Thieves Spying on Your WiFi? - FORTUNE" href="http://www.fortune.com/fortune/fastforward/0,15704,1049542,00.html?promoid=yahoo">this article</a> from David Kirkpatrick over at FORTUNE, and got to thinking.  What the heck is wrong with this scenario?  Then it hit me.</p>
<p>If you keep your double super-dooper secret passwords in a Word document, on an shared access or otherwise unprotected part of your hard drive, you are begging to get hacked.  And that is regardless of whether you sneak access to someone else&#8217;s unsecure wireless access point.</p>
<p>Next time, why don&#8217;t you put the passwords in a text file - then Linux users without <a href="http://www.openoffice.org/">OpenOffice</a> can see them too.</p>
<p>For those of you who understood the sarcasm, please don&#8217;t store your passwords like this.</p>
<!-- sphereit end -->]]></content:encoded>
			<wfw:commentRss>http://michaelgracie.com/2005/04/15/fortune-contributor-victim-of-wifi-hack/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
