<?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: DNS vulnerability details now publicly available</title>
	<atom:link href="http://blog.pfsense.org/?feed=rss2&#038;p=220" rel="self" type="application/rss+xml" />
	<link>http://blog.pfsense.org/?p=220</link>
	<description>News, reviews and more related to the pfSense firewall project</description>
	<lastBuildDate>Fri, 17 May 2013 19:48:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Chris Buechler</title>
		<link>http://blog.pfsense.org/?p=220&#038;cpage=1#comment-1653</link>
		<dc:creator>Chris Buechler</dc:creator>
		<pubDate>Thu, 24 Jul 2008 15:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=220#comment-1653</guid>
		<description><![CDATA[Another explanation if anyone is interested
http://www.avertlabs.com/research/blog/index.php/2008/07/23/the-cat-is-out-of-the-bag-dns-bug/]]></description>
		<content:encoded><![CDATA[<p>Another explanation if anyone is interested<br />
<a href="http://www.avertlabs.com/research/blog/index.php/2008/07/23/the-cat-is-out-of-the-bag-dns-bug/" rel="nofollow">http://www.avertlabs.com/research/blog/index.php/2008/07/23/the-cat-is-out-of-the-bag-dns-bug/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Buechler</title>
		<link>http://blog.pfsense.org/?p=220&#038;cpage=1#comment-1650</link>
		<dc:creator>Chris Buechler</dc:creator>
		<pubDate>Thu, 24 Jul 2008 02:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=220#comment-1650</guid>
		<description><![CDATA[Exploits are now widely available for this. 
http://blogs.zdnet.com/security/?p=1545]]></description>
		<content:encoded><![CDATA[<p>Exploits are now widely available for this.<br />
<a href="http://blogs.zdnet.com/security/?p=1545" rel="nofollow">http://blogs.zdnet.com/security/?p=1545</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Buechler</title>
		<link>http://blog.pfsense.org/?p=220&#038;cpage=1#comment-1648</link>
		<dc:creator>Chris Buechler</dc:creator>
		<pubDate>Wed, 23 Jul 2008 21:43:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=220#comment-1648</guid>
		<description><![CDATA[Beat: Well it would be there with or without you.  :)  But yes, your situation did indeed further bring to light the need to be careful what is providing NAT in your environment. pf&#039;s NAT is excellent from a security perspective - many, many other commercial and open source options are terrible about this and will leave you vulnerable to this particular attack as well as other possible issues in the future.]]></description>
		<content:encoded><![CDATA[<p>Beat: Well it would be there with or without you.  <img src='http://blog.pfsense.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   But yes, your situation did indeed further bring to light the need to be careful what is providing NAT in your environment. pf&#8217;s NAT is excellent from a security perspective &#8211; many, many other commercial and open source options are terrible about this and will leave you vulnerable to this particular attack as well as other possible issues in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beat</title>
		<link>http://blog.pfsense.org/?p=220&#038;cpage=1#comment-1647</link>
		<dc:creator>Beat</dc:creator>
		<pubDate>Wed, 23 Jul 2008 21:27:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=220#comment-1647</guid>
		<description><![CDATA[I feel a bit involvet at least for the last paragraph. Seems like a  abstract from recently discussed thread &quot;[pfSense Support] DNS cache poisoning (solved)&quot;]]></description>
		<content:encoded><![CDATA[<p>I feel a bit involvet at least for the last paragraph. Seems like a  abstract from recently discussed thread &#8220;[pfSense Support] DNS cache poisoning (solved)&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
