<?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: Pastor, secure thy router!</title>
	<atom:link href="http://www.tomsalzer.net/2009/02/pastor-secure-thy-router.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.tomsalzer.net/2009/02/pastor-secure-thy-router.html</link>
	<description>the digital diary of yet another carbon-based unit</description>
	<lastBuildDate>Mon, 22 Mar 2010 17:16:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Tom</title>
		<link>http://www.tomsalzer.net/2009/02/pastor-secure-thy-router.html/comment-page-1#comment-94</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Wed, 11 Mar 2009 23:56:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomsalzer.net/?p=1379#comment-94</guid>
		<description>@Angie, I do limit access by MAC address, but this alone won&#039;t keep unauthorized folks out of your network. I think of it as one more lock on the door, but not a particularly strong lock. Why? Because in most implementations, MAC addresses are passed in the clear, i.e., not encrypted. That means they can be harvested and then used to impersonate an authorized node on your network. Note that I use WPA encryption *and* MAC address filtering. Multiple layers are better than a single layer.</description>
		<content:encoded><![CDATA[<p>@Angie, I do limit access by MAC address, but this alone won&#8217;t keep unauthorized folks out of your network. I think of it as one more lock on the door, but not a particularly strong lock. Why? Because in most implementations, MAC addresses are passed in the clear, i.e., not encrypted. That means they can be harvested and then used to impersonate an authorized node on your network. Note that I use WPA encryption *and* MAC address filtering. Multiple layers are better than a single layer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angie</title>
		<link>http://www.tomsalzer.net/2009/02/pastor-secure-thy-router.html/comment-page-1#comment-93</link>
		<dc:creator>Angie</dc:creator>
		<pubDate>Wed, 11 Mar 2009 21:57:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomsalzer.net/?p=1379#comment-93</guid>
		<description>Tom,

What do you think of using a MAC address list to deny any station access but the ones you own?  Do you feel this is more or less secure than using WPA encryption keys?</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>What do you think of using a MAC address list to deny any station access but the ones you own?  Do you feel this is more or less secure than using WPA encryption keys?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.tomsalzer.net/2009/02/pastor-secure-thy-router.html/comment-page-1#comment-73</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 09 Feb 2009 08:00:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomsalzer.net/?p=1379#comment-73</guid>
		<description>@Sandy, it&#039;s not the wireless nature of the connection that creates vulnerabilities, it is the lack of configuration and active management of the device. Transactions over wired connections can also be intercepted. Don&#039;t let my article scare you away from setting up a wireless connection at home, but do take some time to configure it, enable the firewall in the router, use a strong password/passphrase, and use WPA (preferably WPA2) to secure the wireless connection.</description>
		<content:encoded><![CDATA[<p>@Sandy, it&#8217;s not the wireless nature of the connection that creates vulnerabilities, it is the lack of configuration and active management of the device. Transactions over wired connections can also be intercepted. Don&#8217;t let my article scare you away from setting up a wireless connection at home, but do take some time to configure it, enable the firewall in the router, use a strong password/passphrase, and use WPA (preferably WPA2) to secure the wireless connection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy</title>
		<link>http://www.tomsalzer.net/2009/02/pastor-secure-thy-router.html/comment-page-1#comment-72</link>
		<dc:creator>Sandy</dc:creator>
		<pubDate>Mon, 09 Feb 2009 06:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomsalzer.net/?p=1379#comment-72</guid>
		<description>Timely post. Been thinking of hooking up a wireless network but I&#039;ve been worried about security. Especially since we know there is at least one unsecured network nearby, and can see how easy it is to hop aboard.</description>
		<content:encoded><![CDATA[<p>Timely post. Been thinking of hooking up a wireless network but I&#8217;ve been worried about security. Especially since we know there is at least one unsecured network nearby, and can see how easy it is to hop aboard.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
