<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Lap Cat Software Blog &#187; Uncategorized</title>
	<atom:link href="http://lapcatsoftware.com/blog/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://lapcatsoftware.com/blog</link>
	<description>Coding under the close supervision of cats</description>
	<lastBuildDate>Sat, 24 Jul 2010 13:30:56 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>SECURITY ALERT: check your DNS servers</title>
		<link>http://lapcatsoftware.com/blog/2008/07/22/security-alert-check-your-dns-servers/</link>
		<comments>http://lapcatsoftware.com/blog/2008/07/22/security-alert-check-your-dns-servers/#comments</comments>
		<pubDate>Sun, 02 Aug 2009 15:12:48 +0000</pubDate>
		<dc:creator>Jeff</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://lapcatsoftware.com/blog/?p=75</guid>
		<description><![CDATA[The full details of the infamous DNS vulnerability have been inadvertently disclosed. The post was pulled, but I can still read it in my Vienna database. The vulnerability is bad, folks. I completely agree with the decision to keep the details secret while vendors patch their DNS servers. The secret is out now, though, so [...]]]></description>
			<content:encoded><![CDATA[<p>The full details of the <a href="http://www.kb.cert.org/vuls/id/800113" title="Vulnerability Note VU#800113">infamous DNS vulnerability</a> have been <a href="http://www.matasano.com/log/1105/regarding-the-post-on-chargen-earlier-today/" title="Regarding The Post On Chargen Earlier Today">inadvertently disclosed</a>. The post was pulled, but I can still read it in my <a href="http://www.vienna-rss.org/vienna2.php" title="Vienna">Vienna</a> database.</p>
<p>The vulnerability is bad, folks. I completely agree with the decision to keep the details secret while vendors patch their DNS servers. The secret is out now, though, so there&#8217;s no time to wait. Perform the <a href="https://www.dns-oarc.net/oarc/services/dnsentropy" title="Web-based DNS Randomness Test">web-based test</a> of your DNS servers, and switch to different servers if the results are POOR. If you need to switch, one decent option is <a href="https://www.opendns.com/start" title="Enable OpenDNS">OpenDNS</a>.</p>
<p>Laptop users should be especially careful, because your ISP changes when you take your computer to different locations. Even if you pass the test at home, you may be vulnerable at the coffee shop. I recommend hard-coding DNS server IP addresses in the Network pane of System Preferences. You might also want to check the DNS settings of any routers you use.</p>
]]></content:encoded>
			<wfw:commentRss>http://lapcatsoftware.com/blog/2008/07/22/security-alert-check-your-dns-servers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
