<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Brett Watson &#45; CircleID</title>
		<link>http://www.circleid.com/</link>
		<description>Postings from Brett Watson on CircleID</description>
		<dc:language>en</dc:language>
		<dc:rights>Copyright 2012, unless where otherwise noted.</dc:rights>
		<dc:date>2005-08-17T19:27:38-08:00</dc:date>
		

		
		<item>
			<title> So You Think You're Safe from DNS Cache Poisoning? (Featured Blog)</title>
			<guid isPermaLink="true">http://www.circleid.com/posts/so_you_think_youre_safe_from_dns_cache_poisoning</guid>
			<link>http://www.circleid.com/posts/so_you_think_youre_safe_from_dns_cache_poisoning</link>
			<description><![CDATA[Everyone is probably well aware of the Kashpureff-style DNS cache- poisoning exploit (I'll call this "classic cache poisoning"). For reference, see the [url=http://www.cert.org/advisories/CA-1997-22.html]original US-CERT advisory[/url] prompted by this exploit. Vendors patched their code to appropriately scrub (validate) responses so that caches could not be poisoned. For the next 7-8 years, we didn't hear much about cache poisoning. However, there was still a vulnerability lurking in the code, directly related to cache poisoning. ...On April 7, 2005, the SANS ISC (not to be confused with Internet Systems Consortium) [url=http://isc.sans.org/diary.php?date=2005-04-07]posted an update[/url] detailing how Microsoft Windows DNS servers were still being poisoned, even though the "Secure cache against pollution" option was set. The SANS ISC found that Windows DNS servers using BIND4 and BIND8 servers as forwarders were being poisoned. But how could this be? <a href="http://www.circleid.com/posts/so_you_think_youre_safe_from_dns_cache_poisoning">More...</a>]]></description>
			<dc:date>2005-08-17T19:27:38-08:00</dc:date>
		</item>
		
	</channel>
</rss>
